4 ms·
Yes! Been preaching this for years! I've untangled more than a couple small eng teams (~ < 20 devs) that were trying to do microservices using this recipe on
by mattbillenstein 7y ago
Yes! Been preaching this for years!
I've untangled more than a couple small eng teams (~ < 20 devs) that were trying to do microservices using this recipe on aws and just horrendously failing at it.
A well-architeched monolith will really go a long way - generally perhaps easily up to 100 or more devs before thinking about microservices.
- shantly 7y ago- If it doesn't have very different scaling needs from the rest of the application, probably don't make it a microservice. - If it isn't something you could plausibly imagine using as a 3rd party service (emailer/sms/push messages, authentication/authorization, payments, image processing, et c.) probably don't make it a microservice. - If you don't have at least two applications at least in development that need the same service/functionality, probably don't make a microservice. - If the rest of your app will completely fall over if this service fails, probably don't make it a microservice. - Do write anything that resembles the above, but that you don't actually need to make a microservice yet, as a library with totally decoupled deps from the rest of your program.