6 ms·

I suppose that could be an argument for microservices; use 'boring' tech in the places that necessitate it.

• acdha 6y ago
  Yes – although even “microservice” might be slightly skewing that. I generally like to refer to it as “easily replaced” — i.e. if you have a monolith but it's well organized without broad cross-dependencies, you can swap things out pretty quickly without otherwise changing your deployment model. Maybe that's getting somewhere on the microservice spectrum, maybe not but the key part is really just that you have a well-understood contract for what a component provides and what it depends on.