https://github.com/tejasbubane/book_my_ticket
Ticket booking service using Ruby on Rails
https://github.com/tejasbubane/book_my_ticket
Last synced: 10 months ago
JSON representation
Ticket booking service using Ruby on Rails
- Host: GitHub
- URL: https://github.com/tejasbubane/book_my_ticket
- Owner: tejasbubane
- Created: 2025-01-05T20:31:56.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2025-04-04T21:54:13.000Z (about 1 year ago)
- Last Synced: 2025-06-14T08:09:43.039Z (about 1 year ago)
- Language: Ruby
- Size: 165 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 10
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# README
Simple event ticket booking system built with Ruby on Rails.
* Ruby version: 3.4.1
* Database creation: `bundle exec rails db:create`
* System requirements: Postgresql database running
* Database initialization: `bundle exec rails db:migrate`
* How to run the test suite: `bundle exec rspec`
# Core Functionality
* Registration, login, logout
* Create events, book tickets
* View list of all events, my events, my bookings
# System design and challenges
### Concurrency Handling:
Handles case when multiple users try to book more than available tickets. Multiple levels of checks added in increasing level of complexity:
* **Code level checks:** Limit ticket quantity select dropdown numbers to only available tickets. Check in TicketBookingService to skip if booking not possible.
* **Validation:** ActiveRecord validation to check if sold tickets does not exceed total available tickets. This comes in handy in cases where user has stale browser page open.
* **[Postgres Level Constraint](https://www.postgresql.org/docs/current/ddl-constraints.html):** Add a [DB-level check constraint](https://api.rubyonrails.org/v8.0.1/classes/ActiveRecord/ConnectionAdapters/SchemaStatements.html#method-i-add_check_constraint) when multiple users book in parallel.
* **Row-level lock:** Use [Rails pessimistic locking](https://api.rubyonrails.org/classes/ActiveRecord/Locking/Pessimistic.html) when updating sold ticket count.
### Caching:
* **Fragment Caching:** Use Rails' inbuilt [fragment caching](https://guides.rubyonrails.org/caching_with_rails.html#fragment-caching) for caching event details partials.
# Software design
* **Error handling with monads:** [TicketBookingService](app/services/ticket_booking_service.rb) uses [dry-monads](https://dry-rb.org/gems/dry-monads/1.6/result/) to elegantly handle `Success` and `Failure` cases.
* **Query Object:** [EventsQuery](app/queries/events_query.rb) encapsulates code for fetching created, booked and all events.
* **Custom matcher:** Making tests more readable with [this RSpec custom matcher](spec/support/event_matcher.rb) for checking if data element with event ID exists on the page.
* **Authentication:** Not using [new Rails 8 authentication generator](https://www.bigbinary.com/blog/rails-8-introduces-a-basic-authentication-generator). Hand-rolled authentication using Rails' inbuilt `has_secure_password`.
* **Test Coverage:** Maintain test coverage more than `90%`. Checked using [Simplecov](https://github.com/simplecov-ruby/simplecov).
# Out of scope
Following limitations were assumed and some items were considered out of scope:
* Tickets do not have names and are transferrable.
* Simple one-click ticket booking flow. No payment step - hence no pending status field on tickets.
* Instead of listing all tickets, show booked shows with number of tickets booked.
* No multi-language (i18n).
* No admin role to create events - all users can create events.