You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 13, 2024. It is now read-only.
Events are any real world match instances which contain a snapshot of the match. For instance, in cricket: a ball, a wicket, a substitution, an interruption by nature, a new batsman entering the crease etc are all events.
This particular service will be responsible for accepting the data from client (admin), processing it (if required) and pushing it to other layers of services managing SSE connections to the clients (viewers).
Need for Kafka:
Ensuring no data is lost (consistent writes to DB )and the system is fault tolerant
Managing dead letter queues to ensure chronological delivery of events
Synchronising multiple microservices
Extras to be implemented:
Dedicated logger for Kafka
Unit and Integration testing
All implementations are to be done using the go library sarama
Refer past discussions regarding usage of Kafka and Sarama: #4
All queries and suggestions related to the event streaming service(s) can be done here.