Use of Service Mesh instead of Remoting

Hi,

We would to architect our large Cuba project to be more “cloud native”. Since Cuba framework is somewhat based on a Service Oriented Architecture where we can code the business logic into service beans with service names, would it be possible to replace the “remoting” framework used to call the Middleware services with a ServiceMesh and break each addon ServiceBeans into different microservices ? What would be the limitations ?
This will allow us to update the services without needing to redeploy/restart the whole middleware and perhaps even scale up the services when required.

If it cannot be done in Cuba, can this is implemented in Jmix alternatively ?

We like the rapid / ease of FE + BE development of the framework but we seem to be “left behind” in terms of modern architecture design, lacking the ability to be “cloud native” and microservices ready whilst still gaining from the productivity. We are facing questions from our management on this issue.