Microservising

Having a huge application sometimes means that implementing new things is sometimes a madness of intertwined logic and services.

A monolith is a tough piece to handle, but splitting it into its logical groups makes it easier to handle.

Everyone works by the separation principle, where you do not mix business logic with presentation layer. If that is the case, why mix logics and scopes?

Having a microservice based architecture means that you create the functionality in separate services which communicate between each other, and you scale by distributing the services across servers, replicating as needed. Why should you have to replicate the entire project in order to scale, when the bottleneck is only a fraction of the entire thing?

We can assist if You want to start a new project using the microservice approach by planning for it from the very start.