How do you choose between SQL and NoSQL databases?

Choose SQL (PostgreSQL, MySQL) for structured data requiring ACID transactions, complex JOINs, and strict schema enforcement. Choose NoSQL (MongoDB, DynamoDB, Cassandra) for flexible schemas, massive horizontal scale, high write throughput, and eventual consistency workloads.

When should you choose Vertical Scaling vs Horizontal Scaling?

Start with vertical scaling (adding CPU/RAM to one server) for simplicity. Transition to horizontal scaling (adding more servers) when hardware limits are reached, cost curves become prohibitive, or high availability is required. Horizontal scaling introduces distributed system complexity.

What is the difference between Sharding, Partitioning, and Indexing?

Indexing speeds up read queries within a single table using B-Tree or Hash structures. Partitioning splits a single table into logical physical chunks within one database instance. Sharding distributes rows across multiple distinct database servers using a shard key, scaling write throughput and storage.

How do you scale WebSockets to millions of concurrent connections?

Increase Linux file descriptor limits, use Layer 4 load balancing with sticky sessions, and implement a Redis Pub/Sub backplane so any WebSocket server can relay messages to clients connected to other servers. Pattern: Client → HAProxy → WS Servers ↔ Redis Pub/Sub.

What is the difference between LSI and GSI in DynamoDB?

A Local Secondary Index (LSI) shares the same partition key as the base table but uses a different sort key. It is limited to 10GB per item collection and supports strong consistency. A Global Secondary Index (GSI) uses a completely different partition key, spans all partitions, supports only eventual consistency, and has its own dedicated throughput capacity.

Which database should I use for transactions, user profiles, logs, and analytics?

Use PostgreSQL for financial transactions (ACID compliance). Use MongoDB for user profiles (flexible JSON). Use Cassandra for logs and high-throughput writes (LSM tree). Use Apache Druid for real-time analytics (columnar storage). Use Elasticsearch for search and catalog (inverted index). Use Redis for sessions and caching (in-memory).

How does Consistent Hashing work?

Consistent hashing maps both servers and keys onto a circular ring. A key routes clockwise to the nearest server. When a node is added or removed, only 1/N keys need to migrate (vs nearly 100% in modulo hashing). Virtual nodes (100-200 per server) ensure even distribution and prevent hotspots.

How do you design a distributed rate limiter?

Use a Token Bucket algorithm for burst-friendly limiting. For distributed enforcement across multiple API gateway instances, use Redis with Lua scripts to atomically evaluate and increment counters, preventing race conditions (dirty reads) where concurrent requests could bypass the limit.

Why is Shared Database between microservices an anti-pattern (Database-per-Service)? — System Design Interview Answer & Trade-offs

Architectural Breakdown & AnalysisFAANG Aligned

Allowing multiple microservices to read and write directly to a shared relational database breaks microservice autonomy.

Drawbacks of Shared Databases

Tight Schema Coupling: Modifying a table column in Service A breaks queries in Service B, forcing coordinated deployments.
Resource Lock Contention: High write queries in Order Service consume CPU and lock tables needed by User Service.
Loss of Polyglot Persistence: Forces all services to use the same database engine regardless of data access model suitability.

Database-Per-Service Pattern

Each microservice owns its private database. Other services access data exclusively via published REST/gRPC APIs or asynchronous domain events.

TIP — Legacy Migration Rule

When decomposing monolithic databases, use Change Data Capture (Debezium) to stream updates asynchronously while transitioning to private service DBs.

Key Architectural Comparison

Database Architecture	Microservice Autonomy	Schema Migration Risk	Cross-Service Queries	Blast Radius
Shared Database (Anti-pattern)	Low (All services locked to single DB).	High (Altering table breaks multiple teams).	Trivial SQL `JOIN`.	Critical (Single DB crash takes down entire company).
Database-per-Service	100% Autonomous.	Zero blast radius across services.	Requires API calls or asynchronous CQRS events.	Isolated (Service A outage does not affect Service B).

Why is Shared Database between microservices an anti-pattern (Database-per-Service)?

Drawbacks of Shared Databases

Database-Per-Service Pattern

Key Architectural Comparison

Continue Learning on Being SDE