we're currently trying hard to get into microfrontends and self-contained services. I would say that we understood in some way the base concept.... But we run into a problem if we're talking about our calendar:
The calendar is for us a self-contained service with his own microfrontend, and it's including data from other self-contained services. So far, nothing special. So the idealistic way would look something like that:
Desired self-contained services
But the difference we see to other services is, that the calendar has a lot of events (especially in the month view). So if we would go with the microfrontend approach, we understood that we have to include in every event the microfrontends from the self-contained services "employees", "patients", "treatment" etc.. But this seems for us a big performance disadvantage.
So we decided for now to solve this with an API Gateway. But now we lost the independence between the self-contained services:
Do you have some suggestions for us how to get the advantages of microfrontends & self-contained services if you have such a situation as the calendar? Or would you solve it completely differently?
Tech stack: React for Frontend Java Quarkus for Backend Postgresql as Database