There has been a lot of discussion around the true size of a Micro‐ service. What can be considered “micro”? How many lines of code can it be and still be a Microservice?
These are the wrong questions.
Instead, “micro” should refer to scope of responsibility, and the guiding principle here is the the Unix philosophy of Single Responsibility Principle:
If a service only has one single reason to exist, have one single reason to change, providing a single composable piece of functionality, then business domains and responsibilities are not tangled.
These are the wrong questions.
Instead, “micro” should refer to scope of responsibility, and the guiding principle here is the the Unix philosophy of Single Responsibility Principle:
let it do one thing, and do it well.