Microservices Trivia Questions

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

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

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

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

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.

This is a little-known fact: microservices enable graceful handling of traffic from decommissioned or deprecated services, a concept called 'dark traffic' in observability.

The term emerged around 2011 at a workshop of software architects, though the concept evolved from SOA and earlier practices.