Software Architect's Handbook

Small, focused services

The functionality of a microservice should be small in scope. Each microservice should follow the tenet of the Unix philosophy that advocates for doing one thing and doing it well. Keeping the scope small for each service allows the complexity of the software to be better managed.

Applications with a microservice architecture are easier to understand and modify because every service has a focused responsibility. This allows the services to be developed faster. Smaller solutions are easier to load up and use in an IDE, which increases productivity. In addition, new team members are able to become productive in a shorter amount of time.

A microservice can be developed by a small team. This allows organizations to easily ...