- 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.
- 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.