Please enable JavaScript.
Coggle requires JavaScript to display documents.
1 (MicroServices) Scenarios - Coggle Diagram
1 (MicroServices) Scenarios
Code Reuse
(PoV)
Code replication
Copy code to all microservices
Good approach when code is static.
Challenging if shared code need to change
due to bug fix or added functionality
Shared Library
.jar file
Tracking Dependency is a big challenge.
Heterogenous environment doesn't work.
Benefits
Low code volatility, Versioning
Country specific logic
Shared Service
Good for high code volatility, Heterogenous env
Drawbacks
Performance (due to Latency), Fault tolerance, Versioning
Distributed Transaction
ACID
2 phase commit
Saga
Async
Notification
File upload and download
Separate common service
File download
Authorisation as a (JWT) claim
Resources
https://www.developertoarchitect.com/lessons-microservices.html
https://microservices.io/patterns/data/saga.html
Standard cross cutting concerns
Service Chassis (Shared library)
Service Mesh
Service Template
Plumbing code
Error Handling