- Independent consultant, speaker, and author
- Expertise in microservices, cloud, and continuous delivery
- If you are working in an organization that places lots of restrictions on how developers can do their work, then microservices may not be for you
- The golden rule: can you make a change to a service and deploy it by itself without changing anything else?
- So our architects as town planners need to set direction in broad strokes, and only get involved in being highly specific about implementation detail in limited cases.
- I have also seen many a team’s morale and productivity destroyed by having a mandated framework thrust upon them. In a drive to improve code reuse, more and more work is placed into a centralized framework until it becomes an overwhelming monstrosity.
- Making decisions in system design is all about trade-offs, and microservice architectures give us lots of trade-offs to make
- Much of the role of the technical leader is about helping grow them — to help them understand the vision themselves — and also ensuring that they can be active participants in shaping and implementing the vision too.
- I saw used effectively by one of our teams was to delay the implementation of proper persistence for the microservice, until the interface had stabilized enough
- Book - "Building Microservices"
- Book - "Monolith To Microservices"