Description
Listens to various events and apply them according to subscribed handlers.
Should be located on both master and slave clusters. While there are some events that may appear only on the master cluster, events like user-event will only be available on the same cluster where manager-api with scheduler role is located.
Data flow
Listens to Kafka events.
Input
Kafka group - manager
Evennts
- user custom event (produced within a manager API endpoint)
- subscription-event - for sending emails, updating firebase-chart, etc
- segment - for keeping local segment instances up to date
- quota - to stop/resume campaigns when quota is affected
- campaign-task - to properly handle one-time campaigns and debug tasks
- payment - monitors failed payments and notifies users
- billing-type-change - to control firebase accounts assignments
- subscription-extended - to handle subscription event deliveries
- user-front - to trigger event-based campaigns
- firebase-app - to deactivate an affected firebase account (by excluding it from firebase-chart and marking as inactive in firebase)
Output
- subscriber report event (provide a documentation on how subscriber reports are been generated todo)
- campaign_request (created on user-event received and there is a campaign running for this event)