How to fix too many microservices?
My organization has been overdoing microservice based architecture and inching past 100+ microservices. Any new feature need data from 10+ services and each one need to build a new API / Event to support the usecase. This impose hefty penalty on the feature turn-around time. Any suggestions to come out of this problem?
1 comments
Analyze the business processes by roles, and frame it as a cybersecurity review. How many of your microservices are either switching behavior on caller role (unmaintainable) or overloading roles (security antipattern)? The dirty little secret is that most microservices, like most subclassed information types, only concern one role. The rest is the proper granularity of role-specific services.
(The other dirty little secret is that the temptation to overload roles (and information types) comes from "the database".)
(The other dirty little secret is that the temptation to overload roles (and information types) comes from "the database".)