Microservices are praised because they allow each feature to grow independently. While they shine in the B2C world, where traffic is uniform per user, B2B often grapples with unique traffic…

Siarhei

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Pool architecture offers a solution for scaling challenges in B2B environments by providing dedicated infrastructure for each client. It allows scaling per client, offers security and privacy, and simplifies deployment. Migrating to a dedicated infrastructure involves steps such as migrating the network layer and data layer. However, pool architecture also has pitfalls, including the need for shared code among clients and increased maintenance complexity.

Forget your Microservices! The Unparalleled Benefits of Pool Architecture.

I didn’t like this article. I felt that the title promised one thing, but the substance delivered another.
From the article:
<blockquote>
Imagine your service is this tank. Each client is a fish, and they all share the same infrastructure (the water and the food). You can not feed each fish individually. The only option is to pour food into the tank. If you don’t put enough, the whale shark could eat everything before smaller fishes and let them starve. If you put too much food, each species will eat what they need, but some remaining food will go to waste.
</blockquote>
To me, this is describing the pros and cons of certain styles of multi-tenant architecture. Specifically, it’s advocating a “one monolith per tenant” strategy. It’s not something new or revolutionary. We’ve been doing this stuff for years.
What the article doesn’t do is directly contrast “microservices” or “domain-driven-design” with a new concept. Using “pool architecture” can be done in tandem with microservices.
So why does the article start with, “Forget your microservices!” It doesn’t make sense to me. What is there to forget?