only one database? based on microservices, it should have several?It’s much easier to perform schema updates, because only a single microservice is affected.
decentralize everything. avoid sharing code or data schemas. Data storage should be private to the service that owns the data. Use the best storage for each service and data type. Avoid coupling between services. Causes of coupling include shared database schemas and rigid communication protocols.
not working as team based on each microservice?
micro-frontend: store is per microservice?
how to define bounded context
shell manages the messaging/routing?
cross micro-front end communications?
how can microservices be deployed with non-microfrontend
Is each microservice/micro-frontend a separate codebase?
Polyglot programming. Can some part of the code be written in Rust?
Bounded context: it’s often better to design separate models that represent the same real-world identity in two different contexts.
As a general principle, a microservice should be no smaller than an aggregate, and no larger than a bounded context.
inter-service communication: sync API call or async messaging?
is micro-front-end and microservice 1-on-1 relationship? for each front-end, the backend might be an aggregation of services
team structure with micro-frontend and micro services