Re:Don't start with microservices – monoliths are your friend
by Retric on Thursday December 16, 2021 @04:40PM
(#29584331)
It’s not that odd. Databases, print servers, or web servers for example do something similar with multiple copies of the same software running on a network with different settings. Using a single build for almost identical services running on classified and unclassified networks is what jumps to mind.
[ Parent
| on HN ]
Re:Don't start with microservices – monoliths are your friend
by jameshart on Thursday December 16, 2021 @05:38PM
(#29584957)
To what end?
Code reuse?
Re:Don't start with microservices – monoliths are your friend
by Retric on Thursday December 16, 2021 @05:54PM
(#29585134)
It can be. If you have two large services that need 99+% of the same code and their built by the same team it can be easier to maintain them as a single project.
A better example is something like a chain restaurant running their point of sale software at every location so they can keep operating when the internet is out. At the same time they want all that data on the same corporate network for analysis, record keeping, taxes etc.