ticketing-app

App Overview:

• Users can list a ticket for an event (concert, sports) for sale.
• Other users can purchase this ticket
• Any user can list tickets for sale and purchase tickets
• When a user attempts to purchase a ticket, the ticket is locked for 15 minutes. The user has 15 minutes to enter their payment info.
• While locked, no other user can purchase the ticket. After 15 minutes, the ticket should 'unlock'.
• Ticket prices can be edited if they are not locked.

Different Services to be used -

• auth : Handles user signin/signup/signout

• tickets: Handles ticket creation/editing. Knows whether a ticket can be updated.

• orders: Order creation/ editing

• expiration: Watches for orders to be created, cancels them after 15 minutes

• payments: Handles credit card payments.Cancels orders if payment fails, completed if payment succeeds.

Notes

We are creating a separate services to manage each type of resource. Should we do this for every microservices app? Nope! It depends on your usecase, number of resources, business logic tied to each resource etc. but but featue-based design would be better !

Events Published by Each Service

Order Service

1. ORDER:CREATED

• Ticket service needs to be told that one of its tickets has been reserved and no further edits to that ticket should be allowed
• Payment service needs to know there is a new order that a user might submit a payment for
• Expiration service needs to start a 15 minute timer to eventually time out this order

2. ORDER:CANCELLED

• Ticket service should unreserve a ticket if the corresponding order has been cancelled so this ticket can be edited again
• Payments should know that any incoming payments for this order should be rejected.

Ticket Service

1. TICKER:CREATED / TICKET:UPDATED

• Orders needs to know the valid tickets that can be purchased
• Orders needs to know the price of each ticket

Question.

When should we increment or include the 'version' number of a record with an event?

Increment/Include the 'version' number whenever the primary service responsible for a record emits an event to describe a create/update/destroy to a record.

kubectl create secret generic stripe-secret --from-literal STRIPE_KEY=<YOUR_SECRET>