practicalli / practicalli/clojure-web-services
project: Rich tickets
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 16
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Event ticketing system - high volume events
CQRS architecture
Highly scalable ticket request system receives 10,000 concurrent ticket requests
No processing of ticket sales is done, instead tickets are placed on a ticket request stream
A secondary process processes the ticket requests and sends an asynchronous confirmation to the user if ticket purchase was successful
components
- Reliable message / event stream
- kafka
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by clarifying the proposed CQRS architecture and the Kafka-based ticket request stream, including the required behavior for high-volume requests and asynchronous confirmations. Done requires an agreed implementation scope and a working event-ticketing system meeting those requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure, kafka
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100