Help for owners
My business has too many separate services for a small team to keep up
Short answer
Many separate services help large teams work in parallel. For a small team they mostly add work: more deployments, more monitoring and more places where a failure can hide. Count the services, find out which ones change together, and merge those first. Merge in small, reversible steps, never in one big weekend.
Does this sound like your situation?
- A simple feature needs changes in four or five different services.
- Nobody can explain how a request travels through the system.
- Something fails and it takes hours to find out which service caused it.
- Hosting and monitoring take more time than building features.
- New developers need weeks before they can change anything.
Why does this happen?
The split was done for scale the business does not have
Services are often created because they are fashionable or because a large company uses them. A small team then carries the cost of running many things without having the problem the split was meant to solve.
Services that change together are not really separate
If two services must always be changed and released together, they behave as one application with a network in between. You pay for the separation and get none of its benefit.
Each service needs its own care
Every service needs deployment, logging, alerts, secrets, updates and a person who knows it. With a few developers, that work grows faster than the team.
Failures travel between services
When one service is slow or down, the services that call it slow down or fail too. Without good logging across services the cause is hard to see.
What can I do about it today?
- Ask for a one-page list of servicesAsk for each service's name, what it does, who owns it and how it is deployed. A system that cannot be listed on one page is too hard to run.
- Ask which services always change togetherThe answer is usually the first merge candidates. Ask your developers to show the last ten changes and which services each one touched.
- Check who has access to whatMake sure the hosting account, the code repositories and the monitoring tool are in accounts your company owns. Do not change settings on the live system.
- Hold new services until the review is doneAsk that no further services are added until the existing ones have been reviewed. A new one is easy to add and hard to remove.
- Write down the business problem the split was meant to solveIf nobody can name it, such as one part needing to scale on its own, that is useful information for the review.
When should I bring someone in?
- Outages are hard to diagnose because requests cross many services.
- The team spends more time on deployments than on features.
- You are not sure whether to merge services, and a wrong merge could cause downtime.
How do I handle it?
- Map what existsI draw the services, what each one owns and how they call each other, from the code and the running system, not from old documents.
- Find the true boundariesServices that change together, share a database or cannot run alone are candidates to join. Parts that really scale or change independently stay separate.
- Merge one pair at a timeEach merge is a small change with a backup first, a tested rollback and a check on the live system afterwards.
- Leave the team with fewer moving partsThe result is documented in a short guide that shows each remaining service and why it exists.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Are microservices always a mistake?
No. They can suit large teams or parts that have to scale on their own. The page is about small teams that run more services than they can look after.
Can services be merged without downtime?
That depends on how they are built and deployed. The usual method is to move one piece at a time and keep the old route available until the new one is checked.
Will merging services make the system slower?
It should not for normal business use. The decision is made from measurements of how the system is used, not on assumption.
How was this page made?
I drafted this page with AI assistance. It is general guidance for business owners, not advice for your own system. Found a mistake? Tell me.