Course contentsShow
← Cloud and Infrastructure
Lesson 2558 of 2,98955. Microservices on CloudFree lesson

When to Use Microservices

Decision criteria: team size, domain complexity, scalability needs, and organizational readiness.

When to Use Microservices

You'll learn: The key decision criteria for determining whether microservices architecture is the right choice for your organization.

The Decision Framework

Choosing microservices isn't a default answer—it's a strategic decision that depends on several organizational and technical factors. Think of microservices like switching from a single-family home to a condominium complex: it offers flexibility and independence, but requires infrastructure, governance, and coordination you didn't need before.

Four Critical Decision Criteria

Team Size

Microservices shine when you have multiple independent teams (typically 8+ engineers). Amazon's "two-pizza team" rule applies: if teams are large enough to split ownership, microservices enable parallel development without stepping on each other's toes. A small team maintaining everything benefits more from a monolith's simplicity.

Domain Complexity

When your business has distinct, bounded contexts (user management, payments, inventory), microservices allow each domain to evolve independently. Simple applications with tightly coupled logic don't justify the distributed complexity.

Scalability Needs

If different parts of your system have vastly different scaling requirements—like a payment processor needing 100x more capacity than your admin panel—microservices let you scale services independently, optimizing costs and performance.

Organizational Readiness

Your team must have mature DevOps practices: CI/CD pipelines, monitoring, observability, and incident management. Without these foundations, microservices become an operational nightmare. Can your organization handle deploying and monitoring 15+ services instead of one?

The Reality Check

Starting with a monolith and extracting microservices later is often wiser than premature distribution. You need real-world pain points—not hypothetical scale—to justify microservices' operational overhead.

Key Takeaway: Use microservices when you have multiple teams, clear domain boundaries, differential scaling needs, and strong DevOps capabilities—otherwise, start simpler and evolve.