debugger@dev
New member
- Joined
- Mar 1, 2025
- Messages
- 1
- Programming Experience
- 1-3
Hey everyone,
I’m building a mock event ticketing API in .Net10 and want to ensure it follows best practices, design patterns, and scalable architecture. I don’t just want a working solution—I want to write clean, optimized, and maintainable code. I'm looking to improve my skills in more advanced techniques, so any guidance or feedback is greatly appreciated!
Would Love Input On:
Design Patterns – Best approach for handling different booking flows (Factory, Strategy, etc.).
Handling Long-Running Operations – Background tasks, queues, or worker services instead of polling?
Scalability & Maintainability – How to structure it for future extensions?
Performance Optimization – Best practices for in-memory data handling.
Error Handling & Security – Global exception handling, authentication, and authorization.
Key Constraints & Features:
- Supports EventOnly(succeeds after processing time), VIPPackage(bookings always succeed), and LastMinuteTickets(have a higher failure rate due to limited availability, events happening within the next 30 days) searches.
- No external database – everything stored in-memory.
- Async processing (bookings take 30-60 sec to complete).
- Extendable architecture to add new ticket types in the future.
I’m building a mock event ticketing API in .Net10 and want to ensure it follows best practices, design patterns, and scalable architecture. I don’t just want a working solution—I want to write clean, optimized, and maintainable code. I'm looking to improve my skills in more advanced techniques, so any guidance or feedback is greatly appreciated!
Would Love Input On:
Design Patterns – Best approach for handling different booking flows (Factory, Strategy, etc.). Handling Long-Running Operations – Background tasks, queues, or worker services instead of polling? Scalability & Maintainability – How to structure it for future extensions? Performance Optimization – Best practices for in-memory data handling. Error Handling & Security – Global exception handling, authentication, and authorization.Key Constraints & Features:
- Supports EventOnly(succeeds after processing time), VIPPackage(bookings always succeed), and LastMinuteTickets(have a higher failure rate due to limited availability, events happening within the next 30 days) searches.
- No external database – everything stored in-memory.
- Async processing (bookings take 30-60 sec to complete).
- Extendable architecture to add new ticket types in the future.
