Architecture: The Hard Parts

1. How do I determine the appropriate level of service granularity?

2. • service granularity

3. How do I achieve high semantic coupling and low implementation coupling?

4. • semantic vs implementation coupling

5. How do I create bounded contexts and access data I don’t own?

6. • bounded contexts and access data I don’t own

7. How do I decide between synchronous versus asynchronous communication?

8. • synchronous vs asynchronous communication

9. How do I choose between choreography and orchestration for my workflow?

10. • workflow choreography vs orchestration

    • exercise

11. How do I manage a distributed transaction in microservices?

12. • sagas: distributed transaction in microservices

    • ex

Architecture vs design

axioms:

• service is tested as a single unit

• service is deployed as a single unit

• service that writes data, owns it

• deploying often?/larger-services? is a risk

Mark Richardson's website about architecture

https://www.developertoarchitect.com/

https://www.developertoarchitect.com/lessons/