Please enable JavaScript.

Coggle requires JavaScript to display documents.

Backend System Design - Coggle Diagram

- - - - Key-value store
        Abstraction: hash table
        A key-value store generally allows for O(1) reads and writes and is often backed by memory or SSD. Data stores can maintain keys in lexicographic order, allowing efficient retrieval of key ranges. Key-value stores can allow for storing of metadata with a value.
        DB: Redis, Hazelcast, Riak, Voldemort, Memcache
      - Document store
        Abstraction: key-value store with documents stored as values
        A document store is centered around documents (XML, JSON, binary, etc), where a document stores all information for a given object. Document stores provide APIs or a query language to query based on the internal structure of the document itself. Note, many key-value stores include features for working with a value's metadata, blurring the lines between these two storage types. The data is generally semi-structured & stored in a JSON-like format.
        DB: MongoDB, CouchDB, DynamoDB
      - Wide column store
        Abstraction: nested map ColumnFamily<RowKey, Columns<ColKey, Value, Timestamp>>
        A wide column store's basic unit of data is a column (name/value pair). A column can be grouped in column families (analogous to a SQL table). Super column families further group column families. You can access each column independently with a row key, and columns with the same row key form a row. Each value contains a timestamp for versioning and for conflict resolution. This may seem similar to traditional relational databases, but rather than grouping columns together into tables, each column is stored in a separate file or region in the system’s storage.
        
        Hbase structure example:
        
        ts - timestamp
        DB: Hbase, Bigtable, Cassandra
      - Graph database
        Abstraction: graph
        In a graph database, each node is a record and each arc is a relationship between two nodes. Graph databases are optimized to represent complex relationships with many foreign keys or many-to-many relationships.
      - Time-Series databases
        Time-Series databases are optimized for tracking & persisting time series data.
        Time-series data is primarily used for running analytics, deducing conclusions and making future business decisions looking at the results of the analytics.
        DB: Influx DB, Timescale DB, Prometheus
- - - - Definition
        Redundancy is the duplication of critical components or functions of a system with the intention of increasing the reliability of the system, usually in the form of a backup or fail-safe, or to improve actual system performance.
      - Example
    - - Definition
        Replication means having a number of similar nodes running the workload together. There are no standby or passive instances. When a single or a few nodes go down, the remaining nodes bear the load of the service. Think of this as load balancing.
      - Example
    - - Definition
        A High Availability cluster also known as the Fail-Over cluster contains a set of nodes running in conjunction with each other that ensures high availability of the service.
        The nodes in the cluster are connected by a private network called the Heartbeat network that continuously monitors the health and the status of each node in the cluster. Nodes in a cluster are presenting one service (not multiple).
        A single state across all the nodes in a cluster is achieved with the help of a shared distributed memory & a distributed co-ordination service like the Zookeeper.
      - Example