3 ms·
Don't microservices using shared code correspond to going back to a monolith in disguise?
by richardfey 5y ago
Don't microservices using shared code correspond to going back to a monolith in disguise?
- dboreham 5y agoIn the same sense that a set of C binaries that uses libc is a monolith?
- richardfey 5y agoOnly if your company develops the equivalent of libc and it is clearly in scope for its business.
- azaras 5y agoNo. Sharing code is good. Sharing memory bad.
- jjtheblunt 5y agoperfectly said!
- discreteevent 5y agoSharing memory is pretty easy when you have a garbage collector. Even if you have concurrency you can use messaging without having to put the communicating components into separate processes. And having separate garbage collected virtual machines wastes a lot of memory if you want to have enough headroom for performance in each one.
- pjmlp 5y agoNot when sharing memory is done over OS IPC mechanisms. Which is what you want if the application is to be resilient to crashes and exploits from dynamicallly loaded code.