Seeking a better design pattern than "microservices" My team is looking for new ideas for setting up a complex system that would be much simpler and more scalable than “microservices”, which still seem to be a standard, even though we have been using this pattern for a decade. |
> much simpler
There may be some cross-purpose there.
Checking the definition [1], the approach is like how *nix patterns its tooling. This may not be a good approach for all projects.
This is a professional project, rather than an academic one. And so one of the difficulties is catch-22 of working in a professional setting:
1) Everyone is using approach X. 2) The community that surrounds "Everyone" optimizes products/services to support X. 3) It's hard to do anything but X, as products/services for other things are rare (and expensive).
And so, if you're looking for something else beyond what's fashionable, do you have enough budget and political capital to experiment? If not, then you may have to adapt existing tooling to your project, despite the inefficiencies of doing so.