💻 IT & Coding concepts,
clear in 60 seconds.

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

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

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

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

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

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

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

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.

REST, RPC, and gRPC are different methods for communication in software systems.

Latency is the time for one request, while throughput is how many requests are processed.

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

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

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

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

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

gRPC supports four communication patterns: Unary, Server Streaming, Client Streaming, and Bidirectional Streaming.

Latency, throughput, and response time are key metrics in system performance.

Availability is about access; reliability is about correct performance.

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

A reverse proxy routes client requests to different backend services efficiently.

Microservices can communicate using five key patterns based on their needs.

Failover ensures systems remain operational by managing leader changes during failures.

HTTPS is a secure version of HTTP that encrypts data for safety.

Connection pooling reuses database connections but can cause issues if misconfigured.

HTTP methods tell the server what to do, and status codes tell us the result.

Message queues allow services to communicate asynchronously, improving scalability and reliability.

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

Choosing the right boundaries for microservices is crucial for effective architecture.

The TLS handshake establishes a secure connection for HTTPS, ensuring data safety.

Token Bucket allows burst traffic, while Leaky Bucket smooths out traffic flow.

FAANG engineers use high-level design principles to create scalable systems.

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

Fail-stop means a system stops and stays down, while fail-recover means it can come back but needs to be ready.

Jitter helps spread out client retries to avoid traffic spikes.

Kafka uses state stores to remember previous events in stateful stream processing.

Queues distribute tasks to one consumer, while Pub/Sub broadcasts events to multiple subscribers.

The USE Method helps find and analyze infrastructure bottlenecks in software systems.

Message delivery semantics define how messages are sent in distributed systems and handle failures.

Distributed backpressure helps manage the flow of work between services to prevent overload.

Timeouts in distributed systems indicate suspicion, not confirmed failure.

FAANG interviewers evaluate problem understanding, architecture, scalability, and communication skills.

Lamport Timestamps help order events in distributed systems while preserving causality.

REST API design focuses on creating clean, efficient, and scalable web services.