Please enable JavaScript.

Coggle requires JavaScript to display documents.

Microservice Database - Coggle Diagram

- - - - Banking. you want to see same data at real-time everywhere
      - All DB Copies are updated immediately.
      - Prefer Relational DB
    - - Social Networking or you tube video likes
  - - - Ensures the read value is the latest and updated one
      - if the value isn't the latest, then block the Request till replicas update.
    - - ability to respond to requests at any time
      - fault-tolerance in order to accommodate all requests. System remains operational all the time
      - All clients can find a replica of data, even in case of partial node failures
    - - Network Partitioning, parts of system are located in different networks
      - The system continues to work as expected, even in presence of partial node failure
      - Partition Tolerance is must for Distributed Architecture
  - - - All partitions have same Schema. Data is distributed on Partitions
      - Cassandra No-SQL DB is best example. It has the Nodes and all nodes are connected. Works as Master-less Architecture.
    - - Does Row Splitting
      - Columns of table are distributed on partitions. Frequently accessed columns
    - - Partition data based on bounded context or sub-domain
      - Data is segregated according to use of Bounded Context
- - - - All services are connected on Message Broker and all services perform db activity and report back to Broker. Final Update is performed based on the responses.
    - - Centralized service will control the transaction
      - Single-point of failure