Any concept.
clear in 60 seconds.

L4 and L7 load balancers differ in how they route network traffic based on layers of the OSI model.

API Gateway, Proxy, and Load Balancer serve different roles in managing requests and traffic in systems.

Network partitions occur when servers are operational but can't communicate, affecting system performance.

RPC allows one service to call a function in another service over the network.

Load balancers distribute traffic across multiple servers to enhance performance and reliability.

An API Gateway simplifies client access to backend services in microservices.

gRPC allows efficient communication between services using a structured request-response model.

The TCP 3-way handshake ensures reliable connection establishment between a client and server.

Crash failures stop a service, while network failures disrupt communication.

DNS helps microservices find each other, but it has limitations that may require a service registry.

DNS records like A, CNAME, and MX help route internet traffic and manage services.

DNS resolution translates a URL into an IP address for web access.

The CAP Theorem explains the trade-offs in distributed systems during network failures.

Keep-Alive allows reusing HTTP connections to improve efficiency and reduce overhead.

Service Discovery helps microservices locate each other dynamically without fixed IP addresses.

Elasticsearch has different node roles that help manage data and scale clusters effectively.

A CDN speeds up web applications by caching content closer to users.

Distributed tracing helps track requests across microservices to find delays.

Stateless servers are easier to scale because they don't store user session data locally.