💻 IT & Coding concepts,
clear in 60 seconds.

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

Session-based authentication uses cookies to remember users after login.

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

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

Functional requirements define what a system does, while non-functional requirements define how it performs.

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

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

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

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

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

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

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

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

JWTs allow secure user authentication without needing session storage.

Graceful degradation allows apps to function partially during service failures.

Availability is about access; reliability is about correct performance.

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

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

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

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

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

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

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

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

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

Request-Response asks for a result, while Events notify that something has happened.

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

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

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

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

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

HLD provides an overview of system architecture, while LLD details implementation specifics.

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

Transactions ensure database operations are reliable using ACID properties.

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

Batch processing collects data to process later, while stream processing handles data in real-time.

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

The Cache-Aside Pattern speeds up data retrieval by using a cache to store frequently accessed data.

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

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

Tumbling windows are non-overlapping time segments, while hopping windows can overlap.

Cache penetration occurs when requests for non-existent data overload the database.

Caching helps applications respond faster by serving data from memory instead of hitting the database.