---
title: "Microservicing"
description: "Splitting a monolithic application into independently deployable, independently scalable microservices."
og:
  image: images/app/opengraph/og-microservicing.png
---

# Microservicing

A monolith that's grown for years turns "add one feature" into "untangle everything it touches." Splitting it into logical services doesn't just look cleaner - it makes each piece independently deployable and independently scalable.

![Microservicing](/images/pages/monolith_1.png "Microservicing")

You already separate business logic from presentation. Microservicing is the same principle, one level up: separate logics, separate scopes, separate services that communicate instead of one codebase that does everything.

Scale by distributing services across servers and replicating only the bottleneck - not the entire application every time.

![Microservicing](/images/pages/microservicing.png "Microservicing")

Starting a new project? We plan for a microservice architecture from the [very start](/services/consultancy-system-architecture/), so you're not retrofitting it later.