What data needs to be collected to understand if a new microservice creation is required?

To determine whether creating a new microservice is necessary, the following data should be collected:

• Current architecture and service boundaries: which functions and data are already covered by existing services.
• Volume and nature of load: how heavily the current services are loaded, and if there are bottlenecks.
• Connectivity and dependency of components: how tightly the functions planned to be separated are connected.
• Scalability requirements: whether it is necessary to scale part of the functionality independently of others.
• Deployment and update requirements: whether it is necessary to update part of the system without affecting others.
• Team structure and responsibilities: whether there is a dedicated team to support the new service.
• Security and isolation: whether it is necessary to isolate data or logic for security reasons.
• Technical constraints: such as different technologies, programming languages, or databases.

By gathering this data, one can assess whether a new microservice will improve support, scalability, and system development, or if it will add unnecessary complexity.