Microservices visualised: a story of managerial fears and analysis paralysis - Devoxx Morocco 2016

So you’ve jumped on the hype train, built a bunch of microservices, and got your first releases under your belt. Now what?
Our experiences taught us this is the easy part. With the newly obtained microservices freedom, teams easily plunge into a world of cowboys and unicorns. The big ball of mud is just around the corner. Panic, mayhem and chaos loom over the organisation, waiting for everything to spin out of control. Especially for any enterprise not residing in silicon valley, maintaining some sort of governance and compliancy is essential.

Join this talk to gain some insights in what a microservice architecture means not just for the developer, but also for analysts and managers. What can we as developers do to offer them peace of mind? Visualising the state of the architecture is playing a crucial role here.

This leads us to the microservices dashboard, a brand new open source project, officially launched its first major release at Spring One Platform. Building on top of Spring Boot and Spring Cloud, it visualises your microservice architecture and integrates with tools every microservice architecture benefits from. This ranges from consumer-driven-contract testing over service discovery to hypermedia traversal and more.

Transcript

1. Microservices Visualised A story of managerial fears and analysis paralysis
4. Change one thing,
 Change everything. Such minor changes,
 Such huge consequences.
5. Provisioning 
 new instances for 
 scaling takes ages. Heavy load in one component requires everything to scale up.
7. High-performing IT organizations deploy 30x more frequently with 200x shorter lead times they have 60x fewer failures and recover 168x faster - Puppet labs state of devops report 2015
9. Strong Module Boundaries Distribution Eventual Consistency Independent Deployment Operational Complexity Technology Diversity Security Segmentation Separate Scale-out Parallel Development
10. “If you can't build a monolith, what makes you think microservices are the answer?” Simon Brown
14. What’s the compliancy & maturity of the services?
 How can I accommodate recruitment & knowledge sharing?
 What is the technical debt of the services?
 Which teams do I need to chase?
 Are budget & priorities in line with the architectural goals?
 How do I manage change in a DevOps organisation? “
16. What functionality can I reuse?
 Which resources are exposed by what services?
 Which events & messages are sent back and forth?
 Which services are impacted by a change?
 How does a functional flow travel through the layers of the architecture?
 What is coming up, & can I define the future state of the ecosystem? “
18. 
 Which versions are deployed where?
 
 Are my deployments successful?
 
 Which versions do my dependencies have?
 
 Where can I find everything related to my services? “
23. Health Aggregation Mappings Aggregation Index Aggregation Pact Aggregation
32. Icons created by Gregor Črešnar, Serkan Doğan, lipi, Carlos Salgado, iconsphere, Vicons Designs from the Noun Projects Pictures from www.businessforall.eu, www.solararesort.ca, io9.gizmodo.com, blog.bazaarvoice.com, www.nginx.com
33. https://github.com/ordina-jworks/microservices-dashboard @andreasevers