Microservices Trivia Questions

Netflix famously moved to microservices in the late 2000s to handle massive scale and resilience, sparking widespread adoption.

Microservices can be polyglot, but there's no rule requiring different languages; teams often standardize on a few to reduce complexity.

This is the core benefit: each service can be updated, scaled, and owned by different teams without affecting others.

Microservices often increase network latency due to inter-service communication, which can slow performance compared to in-process calls in a monolith.

Microservices introduce distributed systems complexity (e.g., network failures, data consistency), often increasing costs and operational overhead.

Each microservice typically owns its own database (database-per-service pattern) to avoid tight coupling and enable independent scaling.

By breaking an application into independently deployable services, microservices allow teams to update and release features without redeploying the entire system, a core enabler of continuous delivery.

The term was coined at a software architecture workshop near Venice in May 2011, where a group of architects discussed lightweight, independent services.