Microservices rules #4: Provide a great developer experience
developer experience health development fast flow software delivery metrics microservices rulesContact me for information about consulting and training at your company.
The MEAP for Microservices Patterns 2nd edition is now available
Microservices rules #4: Provide a great developer experience
This article continues the series on microservices rules: what good looks like, a collection of principles and practices that help teams adopt microservices successfully.
The articles in the series are:
1. Practice continuous delivery/deployment
2. Implement fast, automated deployment pipelines
4. Provide a great developer experience (DevEx)
5. Use a deliberative design process
6. Design independently deployable services
7. Design loosely coupled services - part 1, part 2, part 3
9. Develop observable services
10. Big/risky change => smaller/safer and (ideally easily) reversible changes - part 1 - incremental architecture modernization, part 2 - continuous deployment, part 3 - canary releases, part 4 - incrementally migrating users, part 5 - smaller user stories
11.Track and improve software metrics and KPIs
Microservices rules #4 is Provide a great developer experience, the last of four software development rules:
This article explains what developer experience (DevEx) means, why it matters, and how to provide a great DevEx.
Read more (This post is for paying subscribers only)
Need help with accelerating software delivery?
I’m available to help your organization improve agility and competitiveness through better software architecture: training workshops, architecture reviews, etc.
Premium content now available for paid subscribers at 
