Hacker News new | past | comments | ask | show | jobs | submit login

> Ticket registration flows are more complicated than meets the eye, and it was an interesting problem to solve.

Could you share what some of the biggest challenges were? Something like handling concurrent purchases/carts, or?




> Concurrent purchases

This is definitely one of the challenges, since the majority of ticket sales happen in bursts.

Another big one is Stripe or PayPal making mistakes: duplicate events might be sent to my server but that doesn't mean someone bought two tickets. Perhaps an event failed to be sent at all. Or the payment event is fake (rare, but must be managed.)

A final example is that somewhere in the registration flow there's a network glitch: perhaps a confirmation email wasn't sent because the email API was down. How do you patch up these "holes" in a customer's record ASAP? All of these problems might influence and amplify each other too.

Anyway it's definitely solvable but requires programmer effort to scale and fail / recover gracefully.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: