the Macro of Microservices

Slide 1

Slide 1 text

the Macro of Microservices Josh Long (⻰龙之春) @starbuxman jlong@pivotal.io github.com/joshlong

Slide 2

Slide 2 text

project the Josh Long (⻰龙之春) @starbuxman jlong@pivotal.io github.com/joshlong

Slide 3

Slide 3 text

Josh Long (⻰龙之春) @starbuxman jlong@pivotal.io github.com/joshlong a Diminishing Delta between Development & Delivery

Slide 4

Slide 4 text

say open source!

Slide 5

Slide 5 text

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)

Slide 6

Slide 6 text

* Rio de Janeiro * Frankfurt, Germany * Tokyo, Japan AUGUST 26 AUGUST 28

Slide 7

Slide 7 text

No content

Slide 8

Slide 8 text

continuous delivery continuous delivery agility microservices cloud computing continuous integration (the feedback loop)

Slide 9

Slide 9 text

the agile manifesto

Slide 10

Slide 10 text

the agile manifesto & software delivery

Slide 11

Slide 11 text

to the cloud!

Slide 12

Slide 12 text

Source: Adrian Cockcroft   http://www.slideshare.net/adrianco water-scrum-fall increases clock time, waste

Slide 13

Slide 13 text

devops - it’s about systems thinking http://itrevolution.com/the-three-ways-principles-underpinning-devops/ Gene Kim - “the Devops Handbook”

Slide 14

Slide 14 text

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!

Slide 15

Slide 15 text

Amazon.com created AWS to reduce communication cost http://www.wired.com/magazine/2011/11/ff_bezos/all/1 Amazon CEO Jeff Bezos

Slide 16

Slide 16 text

-> | ( ) | ..

Slide 17

Slide 17 text

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

Slide 18

Slide 18 text

writing cloud-native software

Slide 19

Slide 19 text

a monolith might be the right answer

Slide 20

Slide 20 text

microservices enable runtime scale http://theartofscalability.com/ Martin L. Abbot, Michael T. Fisher, the Art of Scalability

Slide 21

Slide 21 text

Source: Adrian Cockcroft   http://www.slideshare.net/adrianco microservices enable feature teams

Slide 22

Slide 22 text

..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:

Slide 23

Slide 23 text

microservices enable bounded contexts

Slide 24

Slide 24 text

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

Slide 25

Slide 25 text

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. “ ”

Slide 26

Slide 26 text

Source: Adrian Cockcroft   http://www.slideshare.net/adrianco iteration enables OODA

Slide 27

Slide 27 text

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

Slide 28

Slide 28 text

OODA requires continuous delivery http://www.slideshare.net/jallspaw/10-deploys-per-day-dev-and-ops-cooperation-at-ﬂickr 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 ﬁrst time we deployed 5 times a day, it worked out.” “ ”

Slide 29

Slide 29 text

so how do i build it?

Slide 30

Slide 30 text

spring boot it’s going to take an API.. lots of them! supports rapid development of production-ready applications and services

Slide 31

Slide 31 text

microservices introduce complexity • service registration & discovery?  (and client-side load balancing) • joined up views of data? • centralized conﬁguration management? • distributed tracing? • stream processing? • single sign-on

Slide 32

Slide 32 text

distributed systems are hard

Slide 33

Slide 33 text

don’t reinvent the wheel

Slide 34

Slide 34 text

spring cloud Apache Zookeeper these logos are all trademark/copyright their respective owners (T-B, L-R):     Netﬂix, amazon.com, Apache Software Foundation, Cloud Foundry, Hashicorp they are ALL great organizations and we love their open-source and their APIs!! *

Slide 35

Slide 35 text

continuous delivery continuous delivery agility microservices cloud computing continuous integration (the feedback loop)

Slide 36

Slide 36 text

Questions? A NEW PLATFORM FOR A NEW ERA Josh Long (⻰龙之春) @starbuxman jlong@pivotal.io speakerdeck.com/joshlong   github.com/joshlong   http://spring.io