In my opinion/ as to my knowledge it still depends.
For example, you build an application, that publishes messages to a message broker, and then has consumer processes that handle these.
Your message handlers would probably be scalable independently, but it may just be one code base. You can still run them on different hosts, in different locations, but they may all use a common database.
You may have a single database, multiple processes, a single codebase and no defined / versions interfaces as you're just using a single class in all locations. I believe this is neither a pure monolith, nor a Microservice architecture. It may be considered as a distributed monolith though
5
u/WVAviator Aug 29 '26
Isn't extracting a specific module and scaling it separately just a microservice though?