X vs Y — side-by-side decisions you'll defend in interviews.
Structured, relational, ACID databases versus flexible, horizontally-scalable non-relational stores.
Redis is a rich data-structure server with persistence and replication; Memcached is a lean, multithreaded string cache. Pick by feature needs vs raw simplicity.
Kafka is a durable, replayable distributed log for streaming; RabbitMQ is a flexible message broker with rich routing and per-message acks. Log vs broker.
REST exposes fixed resource endpoints prone to over/under-fetching; GraphQL offers one flexible query endpoint at the cost of caching and N+1 complexity.
Polling repeatedly asks the server for updates over stateless HTTP; WebSockets hold one persistent bidirectional connection for real-time push. Simplicity vs latency.
Replication copies data for high availability and read scaling; sharding splits data across nodes for write scaling. They solve different problems and are often combined.
Vertical scaling adds power to one machine; horizontal scaling adds more machines. Simplicity and a hard ceiling versus complexity and near-limitless growth.
A monolith is one deployable unit that is simple to build and operate; microservices split it into independently deployable services that scale teams at a cost of distributed complexity.