3 ms·
The boring tech part is especially worth considering what environment you're really working in: if you need to interact with things like enterprise SSO systems
by acdha 6y ago
The boring tech part is especially worth considering what environment you're really working in: if you need to interact with things like enterprise SSO systems or web services, meet regulatory requirements, etc. there can be a lot to be said for being able to install something like a SAML authentication, obscure database or file format library without having to write or significantly contribute to one if that's not your core business goal.
- Tarq0n 6y agoI suppose that could be an argument for microservices; use 'boring' tech in the places that necessitate it.
- acdha 6y agoYes – 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.