Differences

This shows you the differences between two versions of the page.

--- software_architecture:distributed_systems [2024/02/04 14:20] – [Data] skipidar
+++ software_architecture:distributed_systems [2025/03/24 07:01] (current) – skipidar
@@ Line 5: / Line 5: @@
   * https://www.designgurus.io/blog/Consistency-Patterns-Distributed-Systems
   * https://darshanadinushal.medium.com/rabbitmq-in-event-driven-communication-between-microservices-df3a9c38ece9
+TOGAF ADM for Microservice Architecture
+{{https://s3.eu-central-1.amazonaws.com/alf-digital-wiki-pics/sharex/NNdHXHyfyG.png}}
@@ Line 27: / Line 31: @@
   * Ownership by single-services (for independent deployment)
   * Low latency read (responsiveness)
+  * Availability of customer-exposed components
+Capabilities of Architecture:
+  *  have a **single source of true** for each type of data, to **guarantee Consistency**
+    * e.g. by [[https://learn.microsoft.com/en-us/azure/architecture/microservices/model/tactical-ddd|Entity type]]?
+  * Components can serve READ independently of each other, to ensure availibility
+    * when one service goes down - the others can use the read-copy of events
+    * use "Aggregates" to define read-copies schemas with multiple entiteis, grouped by use-case
+  * WRITE is served from single sources of true
+    * use SAGA pattern on "Aggregates" and **synchronous dependency** on "single source of true APIs" to ensure consistency
+    *
 Capabilities of Event-store: