I am the architect of a large financial company, and we are at the beginning of introducing new business-oriented information in different countries.
From the very beginning, the basic idea was to follow microservice-oriented principles as much as possible (and making sure that engineers read the book Building Microservices by Sam Newman).
By now I have come to a crossroads. Our services are primarily JSON REST services using Swagger for automatic documentation, but to use these services in our business processes and to ensure that we do not write business logic to services outside these services, we used Camunda as an orchestra tool. And Kamunda is fine (although some of them viewed Corezoid as an alternative), but somewhat clumsy in what is otherwise an elegant set of services.
Now service orchestration is a concept pretty familiar to most engineers. But this is that I am not entirely satisfied that I still have a central engine that controls everything. It is incredibly expensive to replace later on the road (although it is even cheaper to replace than a monolith). And even if this central engine is divided into several engines (which actually takes place today), this does not necessarily make it much better.
In recent years, there has been a movement with microservices in the direction of choreographic architecture (close to events). It is at this moment that I seek advice from engineers and architects who have encountered similar intersection points.
, , , , - , .
, . , : -, , , , . , -. , . () , .
, , - .
, , . , , - .
, ? , ?