> For the complete documentation index, see [llms.txt](https://docs.starcounter.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.starcounter.io/2.3.2/starcounter/collapsing-the-stack.md).

# Collapsing the Stack

**Time to work smarter, not harder. Find out why making the switch to simplified system architecture is the key to beating slow software and maximizing scalability.**

A software vendor’s primary objectives are to attract new users, adapt to the expectations of existing users, and prevent user outflow — all critical to maintaining the agility, competitiveness, and profitability of a business.

Every time the user base grows, the developer is put under pressure — tasked with scaling the entire user platform to accommodate increased workloads, while keeping the UX response time within a fraction of a second. No easy feat considering the development stacks commonly used today, which present significant [trade-offs between system complexity and scalability](/2.3.2/starcounter/collapsing-the-stack/complexity-and-scalability-tradeoff.md).

This imbalance can be resolved through the adoption of an emerging kind of software technology which takes a [slimmed down approach](/2.3.2/starcounter/collapsing-the-stack/the-future-of-micro-services.md) to the software stack — allowing developers to work smarter, not harder. The [resulting benefits](/2.3.2/starcounter/collapsing-the-stack/10-benefits-of-collapsing-the-stack.md) include agility, competitiveness, and a reduced total cost of ownership.