What are the cons of microservice scaling?
More deployments to manage, network calls add latency and failure modes, and caching is harder because each service has its own cache.
Verify This Answer
Cross-check this information using these trusted sources:
More FAQs in Scalability Comparison: Monolith vs Microservices
Yes. You run multiple instances of the monolith behind a load balancer. For most apps, this scales well. Split into microservices only when different features have very different load patterns.
Each service scales independently. The hot service gets more instances; the cold ones do not. This fits apps where different features have very different traffic patterns.
You scale the whole app even if only one feature is hot, a memory leak in one feature affects all instances, and a long-running request on one instance can slow others.
Still have questions?
Browse all our FAQs or reach out to our support team