Microservices Design Principles: A Lesson on High Cohesion and Low Coupling
2 comments
Services should be designed either as providers, which herd data and do nothing on their own, and workers which actually do stuff but hold no data of their own. Think daemon with a REST api, siting on a database and cronjob implementing some business logic.
This pattern avoids transitive dependencies, especially "errors from faraway lands".
This pattern avoids transitive dependencies, especially "errors from faraway lands".
[deleted]
I’ve recently written a detailed lesson on Microservices Design Principles, covering important concepts like high cohesion, low coupling, and API-first design. If you’re looking to deepen your understanding of microservices or need a refresher, feel free to check it out here.
https://codeandbeyond.in/lessons/lesson1
I’d appreciate any feedback or thoughts!