Re:Starting with microservices
by brundolf on Wednesday January 19, 2022 @05:30PM
(#30001315)
You could even have a mono-repo that holds services which run as separate processes, if you need that. That way you still get the benefits of sharing code, types, version numbers, build processes, etc, which seem like the main headaches with the usual approach.
[ Parent
| on HN ]
We passed right by this mode of operation while migrating from microservices=>monolith. Everything is a separate process but running on the same box. Ran that way for quite some time. We pulled services into the main process one-by-one. It went about as smoothly as one could have hoped for.
Re:Starting with microservices
by jamesfinlayson on Wednesday January 19, 2022 @09:07PM
(#30003439)
I've inherited a project like this - lots of common code in a shared library that gets used by multiple services.
Doesn't work too badly but things have been split out more than they need to be.