Event Migration for new services
When a new services gets introduced into the microservice ecosystem, it needs to be synced up to set up its own state.
Migration:
- Information about which events are needed
- Backend generates "past" events and fires them into the messaging queue
Pro:
- Clean migration
- No communication between backend and new service
- Could be done via a new service that reads from the couchdb
- New services can be scaled to set up the state
Contra:
- If many events are needed, the backend might take some time to recreate events