System Design: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 34: Line 34:
* [[State Transition Diagram]]
* [[State Transition Diagram]]
* [[Distributed Systems]]
* [[Distributed Systems]]
* NoSQL discussion: https://bigdata-ir.com/wp-content/uploads/2017/04/NoSQL-Distilled.pdf NoSQL Distilled by Sadalage, Fowler. (Learning/Systems Design)
* Schemaless: Fowler https://martinfowler.com/articles/schemaless/
* Schemaless: Fowler https://martinfowler.com/articles/schemaless/
=Organizatorium=
=Organizatorium=
* Capacity estimation
* Capacity estimation

Revision as of 23:09, 6 November 2021

External

Internal

Overview

The goals of system design is to build software systems that first and foremost are correct, in that the system correctly implements the functions it was built to implement. Additionally, they should aim to maximize reliability, scalability and maintainability.

A Typical System

Many web and mobile applications in use today are conceptually similar to the generic system described below. The functionality differs, as well as reliability, scalability and maintainability requirements, but most systems share at least several of the elements described here. They have mobile and browser clients, communicate with the backend via HTTP or WebSocket protocols, include a business logic layer deployed as monoliths or micro-services, in most cases in containers managed by a container orchestration system like Kubernetes, persist their data in databases, either relational or NoSQL

TODO

Subjects

Organizatorium

  • Capacity estimation