tags : Distributed Systems, Infrastructure, Design Patterns, Event Sourcing
Comments from the interwebs
- Microservices create boundaries between functionality, and a high degree of friction to moving it. It’s usually bad news if you discover an architectural problem that crosses process boundaries.
- You will be better off building a more monolithic system first and keeping an open discussion about what parts of the code would be good candidates for splitting off, and being fairly careful of moving forward with such efforts in the face of dissenting opinion.
- recommend learning about domain driven design as this lends itself extremely well to service oriented architectures
Resources
- Learning the hard way: Microservices | by Andrew van Rooyen | ITNEXT
- A pattern language for microservices
- Books: Two books by Sam Newman