💻 IT & Coding concepts,
clear in 60 seconds.

Fault domains help prevent multiple servers from failing together in an architecture.

Vertical scaling means upgrading one server, while horizontal scaling means adding more servers.

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

Search engines collect, index, retrieve, and rank documents to provide relevant results.

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

High Availability ensures your application remains operational even during server failures.

Active-Active Architecture uses multiple regions to serve traffic simultaneously for better resilience.

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

Choosing between single and multi-region architecture affects system resilience and cost.

Monolithic and microservices architectures each have unique advantages and challenges for software development.

Stream Processing Architecture helps turn incoming events into real-time insights efficiently.

SSRF is a vulnerability where an attacker tricks a server into making unintended requests.

A single component's failure can take down your entire application, even with redundancy.

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

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

Containers share the host OS kernel, while VMs virtualize hardware with separate OS.

Sharding splits databases into smaller parts to improve performance and scalability.

OLTP handles transactions while OLAP is for data analysis and reporting.

Database per Service ensures each microservice owns its data, reducing dependencies.

Database replication enhances data availability and read performance but has challenges like replication lag.

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

Timeouts in distributed systems indicate suspicion, not confirmed failure.

Microservices and modular monoliths differ mainly in deployment and communication methods.

Distributed caching spreads data across multiple servers for better performance and reliability.

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

Distributed locks ensure only one server performs a task, avoiding duplication.

Active-passive architecture ensures a standby system takes over if the main system fails.

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

Authentication verifies who you are, while authorization determines what you can do.

Choosing between a shared database and a database per service affects system design significantly.

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

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

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

Secure API design requires multiple strategies to protect sensitive data and access.

The Bulkhead Pattern isolates resources to protect critical workloads from failures.

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

Elasticsearch uses shards for data distribution and replicas for redundancy.

Microservices are useful when you need independent scaling, deployment, and clear boundaries in software design.

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

Scaling databases involves deciding whether to enhance read or write capabilities based on traffic patterns.

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