6. MIRCOSERVICES GROUND RULES
• Make sure you are solving business problems
• Service customer needs first
• Embrace your monoliths
• Control the tire fire
• Be incremental
• You will have to rethink everything
6
7. MIRCOSERVICES GROUND RULES CONT.
• Create ambassadors
• Stay in the “success zone”
• Eat your own dog food
• Make the running environment the current
authority
7
8. THE CATALYST
• Container revolution
• Single artifact that is re-deployable
• Kick the can approach - Incremental revolution
8
9. CURRENT STATE OF PLAY
• Opinionated common pipeline and platform
• Modular elements
• All new services in containers
• Container orchestration
• New tooling
9
10. DEAD BODIES
• Trouble in paradise
– RPC
– Circular dependencies
– Maintaining consistent service contract points
– Distributed tracing
– Latencies
10
11. KEY TAKEAWAYS
• Be incremental
• Fail fast
• Keep it simple
• Opinion matters
• Chase the MVP not perfection
11
Dialogue!
Speaking from experience
This is a reflection
Platform perspective
Specifically, we build customer communities and social media monitoring tools for a ton of big brands like Virgin, Best Buy, Skype, AT&T and Autodesk.
The confluence of Cloud, DevOps and breaking down barriers
Moving to a model where Dev not only managed writing off their app, but also the deployments
Critical problem – Not services customers
Solving the problem operationally
All your time is spent on infrastructure and not changing the App Dev experience
Devs found it harder to deploy applications
It was easier to deploy to baremetal
We’d changed the infrastructure but not the app deployment
Speaking from experience
No one is green field
No one is green field
Focused on App Dev and provided means to quickly iterate
Sequentially solving problems
Disrupted ourselves. We’ve been hacking at docker for about a year.
Are containers necessary, no but they helped