3 ms·
"one or many services" is also not a Really Big Deal. You can have a few services that do a category of things and not even sniff microservices architecture.
by TameAntelope 4y ago
"one or many services" is also not a Really Big Deal. You can have a few services that do a category of things and not even sniff microservices architecture.
It's not a boolean, it's a spectrum, and where precisely you land on that spectrum is not as important if you're actually focused on getting work done.
- lolinder 4y agoIt's a spectrum, yes, and adding an extra service might be the right move, especially if they are well and truly independent (don't interact with each other). But it's still a significant architectural decision to go for a distributed system, much more so than whether you split your services into separate repos or go for a monorepo. Getting work done is important, but it's not an excuse to avoid thinking through the long-term implications of your decisions. If you shrug and say "it's just one more service" every time you're tempted to add a new docker image, you'll not just end up with microservices, you'll end up with poorly planned microservices.