When people talk about scalability in the cloud, it tends to sound like a property the infrastructure simply has. In practice, real horizontal scalability (the ability to grow by adding resources without rebuilding the system) depends on a concrete architectural decision: microservices. It is worth clearing up the idea that it is automatic, because it is not, and understanding what adopting it involves.
What microservices architecture is, concretely
Microservices architecture divides an application into small, independent components, each responsible for a specific function, that can be developed, deployed, and scaled individually. This is what enables real horizontal scalability: instead of scaling the entire application as a monolithic block, each component scales according to its own specific needs.
On Drupal and Acquia Cloud, this means a module under high demand (for example, a search service or a heavily queried API endpoint) can scale independently, without needing to replicate the entire application to sustain that specific load.
Why this matters for the business, not just the architecture
This way of scaling has direct, measurable consequences. It improves user experience: a site built with microservices can handle traffic spikes and intensive workloads without compromising speed or functionality, because the component under pressure scales without dragging down the rest of the system.
It enables business growth without technological limitations: as an organization expands its user base, launches new services, or enters new markets, a site with this architecture adapts without requiring a complete restructuring. And it reduces operational costs, because only the component that actually needs more resources scales, not the entire application, optimizing infrastructure use against significant, unnecessary investments.
It also increases resilience: if one component fails, the rest of the system can keep operating, minimizing downtime and enabling faster recovery from disruptions, compared to a monolith where a failure can affect the entire system.
What microservices architecture does not solve for free
Here is the point rarely mentioned alongside the benefits. Splitting an application into independent components is not free: it introduces orchestration complexity (coordinating multiple services that used to be one), the need for distributed observability (monitoring the state of several components instead of one), and a larger operational surface (more pieces that can fail in different ways, requiring a team with the maturity to operate them).
A well-built monolith, for a moderately complex project, can be easier to operate than a microservices architecture oversized for the actual scope of the problem. The question is not whether microservices is better in the abstract, but whether the project's scale justifies the additional operational complexity it brings.
How to achieve this architecture with Drupal and Acquia Cloud
Using the right technologies is the starting point: Drupal offers content management with a flexible architecture well suited to a microservices approach, and Acquia Cloud provides the cloud infrastructure that lets you add resources to specific components as needed, without service interruptions.
On that foundation, adopting microservices with judgment means identifying which application components genuinely benefit from scaling independently (those with high demand or high traffic variability), and which can keep operating as part of a more monolithic core without limiting the project's growth.
The decision underneath
Scalability is not a property the cloud grants automatically. It is the result of architectural decisions, and microservices is the concrete decision that makes it possible in practice on Drupal and Acquia Cloud. But adopting it makes sense when the project's scale justifies the operational complexity it brings, not as a default applied to any project.
If your organization wants to review whether your platform needs a microservices architecture, or whether a more consolidated approach is still enough for your current scale, let's sit down to evaluate it.