I like to think of it more of a separation of components needed to do the job. Need a database, use a database as it's own service, don't couple the database t

I like to think of it more of a separation of components needed to do the job. Need a database, use a database as it's own service, don't couple the database to the app, so if you need to scale the app horizontally you can add more replicas. If you need to scale the database vertically, you can scale the database vertically. If these are coupled, you scale only whats needed. On top of that use the language or tool that is meant for the job. If you need something written in go, build your service with go, if you need nodejs, do it with node, etc. Microservices don't need to be micro or small