Migration from Monolith to Microservices Google Cloud
Notes:
- Each microservice should have it’s own database
- All database transactions should be atomic. So if there are any transactions that are “cross-service” and the databases of all the services need to be updated, the entire transaction should be atomic.
- This means that in case one of the transactions fail, the previous transactions must be rolled back.
- A service should probably manage those transactions - use a message queue where applicable
- Need to understand if it is worth it to migrate given the drawbacks
Last update :
25 mai 2024
Created : 25 mai 2024
Created : 25 mai 2024