the Macro of Microservices

this is the deck that accompanies my keynote talk on understanding the larger context around microservices, beyond the mere technology implications

1. the Macro of Microservices Josh Long (⻰龙之春) @starbuxman jlong@pivotal.io github.com/joshlong
2. project the Josh Long (⻰龙之春) @starbuxman jlong@pivotal.io github.com/joshlong
3. Josh Long (⻰龙之春) @starbuxman jlong@pivotal.io github.com/joshlong a Diminishing Delta between Development & Delivery
4. say open source!
5. Josh Long (⻰龙之春) the Spring Developer Advocate • http://cloudnativejava.io • @starbuxman • jlong@pivotal.io • Java Champion • open-source contributor 
 (Spring Boot, Spring Cloud, Spring Integration, Vaadin, Activiti, etc etc)
6. * Rio de Janeiro * Frankfurt, Germany * Tokyo, Japan AUGUST 26 AUGUST 28
8. continuous delivery continuous delivery agility microservices cloud computing continuous integration (the feedback loop)
9. the agile manifesto
10. the agile manifesto & software delivery
11. to the cloud!
12. Source: Adrian Cockcroft 
 http://www.slideshare.net/adrianco water-scrum-fall increases clock time, waste
13. devops - it’s about systems thinking http://itrevolution.com/the-three-ways-principles-underpinning-devops/ Gene Kim - “the Devops Handbook”
14. cloud helps automate operations http://www.computerweekly.com/opinion/Value-chain-mapping-learning-to-use-IT-as-a-strategic-weapon Simon Wardley, Value Chain Mappings platform!
15. Amazon.com created AWS to reduce communication cost http://www.wired.com/magazine/2011/11/ff_bezos/all/1 Amazon CEO Jeff Bezos
16. -> | ( ) | ..
17. Imagine if architects had to be the janitor for every building they designed. This is how the development team felt prior to moving to Windows Azure. “ Cloud Foundry: day # 2 ” http://infoq.com/articles/Channel-9-Azure Duncan Mackenzie - Nov 07, 2011
18. writing cloud-native software
19. a monolith might be the right answer
20. microservices enable runtime scale http://theartofscalability.com/ Martin L. Abbot, Michael T. Fisher, the Art of Scalability
21. Source: Adrian Cockcroft 
 http://www.slideshare.net/adrianco microservices enable feature teams
22. ..organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations Conway’s to understand your service boundaries corollary: you can refactor your organization to improve your systems Mel Conway’s law:
23. microservices enable bounded contexts
24. microservices enable iteration agile programming unit testing & TDD scrum continuous integration … modern computer science values quantity, velocity over quality if you wait for all the data to make an informed decision, it may be too late to make any decision at all
25. OODA requires continuous delivery Adrian Cockcroft, former SVP of Web Engineering @ Netflix if you say “I’m doing this because it’s more efficient,” the unintended result is that you’re slowing someone else down. This is not an encouragement to be wasteful, but you should optimize for speed first. Efficiency becomes secondary as you satisfy the constraint that you’re not slowing things down. The way you grow the business to be more efficient is to go faster. “ ”
26. Source: Adrian Cockcroft 
 http://www.slideshare.net/adrianco iteration enables OODA
27. source: Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation / Jez Humble, David Farley. ISBN 978-0-321-60191-9 OODA requires continuous delivery
28. OODA requires continuous delivery http://www.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-flickr John Allspaw - Flickr (not Etsy) We may deploy 20 times a day, but we wouldn’t deploy 20 times a day if we went down 20 times a day. The only reason we got to 20 times a day, is that the first time we deployed 5 times a day, it worked out.” “ ”
29. so how do i build it?
30. spring boot it’s going to take an API.. lots of them! supports rapid development of production-ready applications and services
31. microservices introduce complexity • service registration & discovery?
 (and client-side load balancing) • joined up views of data? • centralized configuration management? • distributed tracing? • stream processing? • single sign-on
32. distributed systems are hard
33. don’t reinvent the wheel
34. spring cloud Apache Zookeeper these logos are all trademark/copyright their respective owners (T-B, L-R): 
 
 Netflix, amazon.com, Apache Software Foundation, Cloud Foundry, Hashicorp they are ALL great organizations and we love their open-source and their APIs!! *
35. continuous delivery continuous delivery agility microservices cloud computing continuous integration (the feedback loop)
36. Questions? A NEW PLATFORM FOR A NEW ERA Josh Long (⻰龙之春) @starbuxman jlong@pivotal.io speakerdeck.com/joshlong 
 github.com/joshlong 
 http://spring.io