The idea behind using a microservice is that the code base is split up into distinct areas, each independently responsible for a specific function or business capability, and can be developed, tested, and deployed independently of the other services in the application.

Some of the potential downsides of using microservices include:

Complexity – microservices can be more complex to develop and maintain than a monolithic application because they require coordination between multiple services.
Debugging and troubleshooting – microservices can be more difficult to debug and troubleshoot because errors can be hard to track down when they span multiple services.
Latency and speed – the communication between microservices can add overhead and increase latency, which can impact the performance of the overall system.
Cost – microservices can be more expensive to operate because they require more infrastructure to support the individual services.

having a birdseye view of your applications help you and your team identify potential security risks. One of the most common ways products are left vulnerable to attacks these days is through endpoint exposure.

poor architectural decisions will inevitably impact your ability to scale.

build to change, don’t build to last. Strong tech leads will anticipate change and build solutions in ways that anticipate change further down the line. Service oriented architecture embodies this principle since it anticipates further changes and allows new, interoperable services to be introduced in the future