software_architecture:distributed_systems
This is an old revision of the document!
Table of Contents
distributed_systems
Event driven architecture
Event-store
Data
Non functional requirements NFRs:
- Consistency (across distributed landscape)
- Ownership by single-services (for independent deployment)
- Low latency read (responsiveness)
Capabilities of Event-store:
- when service is down, then replay missed events from event store
- replay missed events from the beginning of time
- create snapshots, to avoid replaying the complete history replay
- convert event schemas, to convert old history into new format, when schemas change
INfos
software_architecture/distributed_systems.1707055341.txt.gz · Last modified: by skipidar