Please enable JavaScript.
Coggle requires JavaScript to display documents.
distributed system - Coggle Diagram
distributed system
-
-
distributed system
-
-
a collection of interconnected nodes that share data. Client writes data to any of these nodes and reads data by contacting with any of these nodes
Data Layer
-
CAP Theorem
Consistency
all clients see the same data, i.e. the latest write and consequent read returns newest data
Availability
system can process requests even when some nodes are down, in a reasonable amount of time and doesn't return an error or hang
Partition tolerance
-
network partition is a breaking connectivity, therefore we always need to have partition tolerance cause we can't be sure about the network
-
for a pair of 2 requests, a write followed by read, a distributed system can promise to guarantee only 2 out of 3 from CAP
-
-
-
scalability
-
horizontal
-
statelessness
To scale horizontally without problems, we have to move state management (user sesssion, memory, local files, resource lcoks) from frontend to backend
-
-
Backend Layer Components
-
achieving statelessness
no shared store - use cache, database or message queue
-
-
-
SSL Termination
SSL termination intercepts encrypted https traffic when a server receives data from a secure socket layer (SSL) connection in an SSL session. SSL termination or SSL offloading decrypts and verifies data on the load balancer instead of the application server. Spared of having to organize incoming connections, the server can prioritize on other tasks like loading web pages. This helps increase server speed. SSL termination represents the end — or termination point — of an SSL connection.
-