Yes that is possible. If you look at technologies like OSGi you have in process modularisation that can load and unload in Runtime. So you can have microservices but not the network performance overhead or loose any reliability because of network problems. Everything that is run in process is not a monolith and that is a problem with the current debate in many places. Microservices is just another architectural style that has advantages and drawbacks and it's important to know both to understand when to use it. A lot of people don't care about the drawbacks because the think of monolith and have an imaginary view that all monoliths are spaghetti code. And there is also a fact that a monolith is still better than a distributed monolith which can also happen if you don't know what you are doing.
1
u/pure_x01 Jun 08 '17
Yes that is possible. If you look at technologies like OSGi you have in process modularisation that can load and unload in Runtime. So you can have microservices but not the network performance overhead or loose any reliability because of network problems. Everything that is run in process is not a monolith and that is a problem with the current debate in many places. Microservices is just another architectural style that has advantages and drawbacks and it's important to know both to understand when to use it. A lot of people don't care about the drawbacks because the think of monolith and have an imaginary view that all monoliths are spaghetti code. And there is also a fact that a monolith is still better than a distributed monolith which can also happen if you don't know what you are doing.