--- title: "How (not) to cut microservices" url: https://daily.dev/posts/how-not-to-cut-microservices-lqatiikkv source_url: https://event-driven.io/en/how_to_cut_microservices type: article source: "Event-Driven by Oskar Dudycz" published: 2026-06-17T11:26:14.782Z updated: 2026-06-17T11:32:02.024Z tags: ["career", "cicd", "microservices", "distributed-systems"] reading_time: 5 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # How (not) to cut microservices **[Event-Driven by Oskar Dudycz](https://daily.dev/sources/event-driven-io)** · 5 min read · 0 upvotes · 0 comments ## Summary A practical discussion on when it actually makes sense to split an application into multiple deployment units (microservices). Four legitimate technical reasons are outlined: differences in traffic/workload across modules, need for horizontal scaling during peak load, multi-tenancy with data isolation (sharding), and multi-region deployments. Two common but questionable justifications are also challenged: pursuing 100% availability at all costs, and splitting services purely based on storage type. The post argues that microservices should be driven by real technical needs, not cargo cult or buzzword adoption. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [When to Use Microservices \(And When Not To\) in .NET](https://daily.dev/posts/when-to-use-microservices-and-when-not-to-in-net-bexpylmbp) · Code with Mukesh · 12 upvotes · 0 comments --- Tags: [#career](https://daily.dev/tags/career), [#cicd](https://daily.dev/tags/cicd), [#microservices](https://daily.dev/tags/microservices), [#distributed-systems](https://daily.dev/tags/distributed-systems) [View this post on daily.dev](https://daily.dev/posts/how-not-to-cut-microservices-lqatiikkv)