made for each other: microservices + paas

40
DevOps, microservices, & the new composable enterprise Donnie Berkholz @dberkholz

Upload: pivotal

Post on 04-Jul-2015

1.427 views

Category:

Technology


1 download

DESCRIPTION

Companies need to build better software faster to compete. But existing monolithic applications, legacy platforms, and lengthy operational deployment cycles are holding innovation back. Microservices are becoming the cloud architecture of choice because they offer the ability to loosely couple applications into discrete services that can be surgically changed without requiring disruptive overhauls. This approach enables the responsiveness and rapid change needed by the business. Enterprise PaaS is a critical foundation to simplify the operations, governance, and health management of these new architectures. Together with a DevOps culture, microservices and PaaS are the engine that drives innovation at speed.

TRANSCRIPT

Page 1: Made for Each Other: Microservices + PaaS

DevOps, !microservices,!& the new !composable enterprise

Donnie Berkholz!@dberkholz

Page 2: Made for Each Other: Microservices + PaaS

What in the world !is DevOps, anyhow?

Page 3: Made for Each Other: Microservices + PaaS

Agile, truly tip to tail Business to customer

Page 4: Made for Each Other: Microservices + PaaS

Flickr: kalandrakas

Tear down all the silos

Page 5: Made for Each Other: Microservices + PaaS

“Infrastructure as code”

Page 6: Made for Each Other: Microservices + PaaS

#monitoringsucks/#monitoringlove

Page 7: Made for Each Other: Microservices + PaaS

Organizations with high performing DevOps organizations were 2x more likely to exceed profitability, market share and productivity

goals…!!!!!

Source: Puppet Labs 2014 State Of DevOps Gene Kim

…and had 50% higher market capitalization growth over 3 years…

Page 8: Made for Each Other: Microservices + PaaS

Who Is Doing DevOps? § Google, Amazon, Netflix, Etsy, Spotify, Twitter, Facebook … § CSC, IBM, CA, SAP, HP, Microsoft, Red Hat … § GE Capital, Nationwide, BNP Paribas, BNY Mellon, !

World Bank, Paychex, Intuit … §  The Gap, Nordstrom, Macy’s, Williams-Sonoma, Target … § General Motors, Northrop Grumman, LEGO, Bosche … § UK Government, US Department of Homeland Security … § Kansas State University…

Who else?

Gene Kim

Page 9: Made for Each Other: Microservices + PaaS
Page 10: Made for Each Other: Microservices + PaaS

CI/CD & the !changing roles !of Devs and Ops

Page 11: Made for Each Other: Microservices + PaaS

Test your infrastructure like your code

Page 12: Made for Each Other: Microservices + PaaS

The composable enterprise! and the Yegge memo

Page 13: Made for Each Other: Microservices + PaaS

Containerization

Page 14: Made for Each Other: Microservices + PaaS

Stack Overflow container traction

Page 15: Made for Each Other: Microservices + PaaS

Microservices (not monoliths)

Separation of (business) concerns into services accessed via REST APIs

Resilient to failure, easily reusable, etc

Page 16: Made for Each Other: Microservices + PaaS

Platform as a Service (PaaS)

Has its time finally arrived?

Page 17: Made for Each Other: Microservices + PaaS

The view from 40,000 feet

continuousautomation.com

Page 18: Made for Each Other: Microservices + PaaS

Minimizing risk, Maximizing agility

l  Architecture: Microservices, monitoring l  Code: Continuous integration, feature flags l  Servers: Continuous delivery, infrastructure as code l  Services: Rolling updates, resilient engineering l  Product: Continuous deployment, restricted audience

Page 19: Made for Each Other: Microservices + PaaS

Donnie Berkholz [email protected] Twitter/IRC: dberkholz

Page 20: Made for Each Other: Microservices + PaaS

‹#› © 2014 Pivotal Software, Inc. All rights reserved. © 2014 Pivotal Software, Inc. All rights reserved.

Made for Each Other: Microservices + PaaS How Pivotal CF and Spring Cloud Enable Architectural Innovation

Matt Stine (@mstine) Platform Engineer

Page 21: Made for Each Other: Microservices + PaaS

21 © 2014 Pivotal Software, Inc. All rights reserved.

Infrastructure

Applications

Monoliths

Microservices

Physical/Virtual Pivotal CF Continuous Delivery

DevOps

Feedback Rapid Iteration

Horizontal Scale

Diversity of Clients

Page 22: Made for Each Other: Microservices + PaaS

22 © 2014 Pivotal Software, Inc. All rights reserved.

New Architectural Constraints

•  Pivotal CF optimizes for 12 Factor Linux applications

Page 23: Made for Each Other: Microservices + PaaS

23 © 2014 Pivotal Software, Inc. All rights reserved.

Twelve Factors

• One Codebase/Many Deploys •  Explicit Isolated

Dependencies • Config via Environment • Attached Backing Services •  Separate Build/Release/Run •  Stateless Processes •  Export Services via Port

Bindings

•  Scale Out via Processes • Disposable Instances • Dev/Prod Parity •  Logs == Event Streams • Admin Tasks == Processes

Page 24: Made for Each Other: Microservices + PaaS

24 © 2014 Pivotal Software, Inc. All rights reserved.

New Architectural Constraints

•  Pivotal CF optimizes for 12 Factor Linux applications •  Microservices: a radical departure from traditional

monolithic applications •  In both cases, the enterprise is

forced to “think different.”

Page 25: Made for Each Other: Microservices + PaaS

25 © 2014 Pivotal Software, Inc. All rights reserved.

How XP Practices Support Each Other

http://www.kusmin.eu/wiki/index.php/How_XP_Practices_Support_Each_Other

Page 26: Made for Each Other: Microservices + PaaS

26 © 2014 Pivotal Software, Inc. All rights reserved.

A Mutualistic Symbiotic Relationship…

Microservices Pivotal CF

http://en.wikipedia.org/wiki/Symbiosis#Mutualism

Page 27: Made for Each Other: Microservices + PaaS

27 © 2014 Pivotal Software, Inc. All rights reserved. 27 © 2014 Pivotal Software, Inc. All rights reserved.

http://highscalability.com/blog/2014/4/8/microservices-not-a-free-lunch.html

Page 28: Made for Each Other: Microservices + PaaS

28 © 2014 Pivotal Software, Inc. All rights reserved.

Paying for your lunch…

•  Significant Operations Overhead •  Substantial DevOps Skills Required •  Implicit Interfaces • Duplication of Effort • Distributed System Complexity • Asynchronicity is Difficult! •  Testability Challenges

Page 29: Made for Each Other: Microservices + PaaS

29 © 2014 Pivotal Software, Inc. All rights reserved.

You must be this tall to use Microservices…

•  RAPID PROVISIONING •  BASIC MONITORING •  RAPID APPLICATION

DEPLOYMENT •  DEVOPS CULTURE

http://martinfowler.com/bliki/MicroservicePrerequisites.html

https://www.flickr.com/photos/gusset/3723961589

Page 30: Made for Each Other: Microservices + PaaS

30 © 2014 Pivotal Software, Inc. All rights reserved.

It’s gonna take a platform…

Pivotal CF Spring Cloud

Page 31: Made for Each Other: Microservices + PaaS

31 © 2014 Pivotal Software, Inc. All rights reserved.

Platform Features

• Environment Provisioning • On-Demand/Automatic Scaling • Failover/Resilience • Routing/Load Balancing • Data Service Operations • Monitoring

• Distributed/Versioned Config • Service Registration/Discovery • Routing/Load Balancing • Service Integration • Fault Tolerance • Asynchronous Messaging

Page 32: Made for Each Other: Microservices + PaaS

32 © 2014 Pivotal Software, Inc. All rights reserved.

http://projects.spring.io/spring-cloud

Page 33: Made for Each Other: Microservices + PaaS

33 © 2014 Pivotal Software, Inc. All rights reserved.

•  Eureka •  Hystrix + Turbine •  Ribbon •  Feign •  Zuul •  Archaius

+

http://netflix.github.io

Page 34: Made for Each Other: Microservices + PaaS

34 © 2014 Pivotal Software, Inc. All rights reserved.

Pivotal CF + Spring Cloud + Netflix OSS!

Live Demo https://www.youtube.com/watch?v=vm8PcbcsYxU#t=2787

Page 35: Made for Each Other: Microservices + PaaS

35 © 2014 Pivotal Software, Inc. All rights reserved.

Supporting Rapid Change

Microservices is the first architectural style developed:

POST

POST &

Continuous Delivery

DevOps ∆

Page 36: Made for Each Other: Microservices + PaaS

36 © 2014 Pivotal Software, Inc. All rights reserved.

Architecture is abstract until it is operationalized.

Neal Ford

Page 37: Made for Each Other: Microservices + PaaS

37 © 2014 Pivotal Software, Inc. All rights reserved.

Architectures that aren’t operationalized exist only on whiteboards.

Matt Stine

Page 38: Made for Each Other: Microservices + PaaS

38 © 2014 Pivotal Software, Inc. All rights reserved.

OPERATIONALIZED ARCHITECTURE

Microservices

Pivotal CF

Spring Cloud

Page 39: Made for Each Other: Microservices + PaaS

39 © 2014 Pivotal Software, Inc. All rights reserved.

Thank you!

•  @dberkholz •  "The interface from Dev to Ops isn’t going away; it’s rotating” bit.ly/devops-rotating

•  "The parallel universes of DevOps and cloud developers” bit.ly/devops-parallel

•  "DevOps and cloud: A view from outside the Bay Area bubble" bit.ly/devops-bubble

Cloud Foundry

twitter.com/cloudfoundry

youtube.com/user/CloudFoundry

Spring

twitter.com/springcentral

spring.io/video

Page 40: Made for Each Other: Microservices + PaaS

40 © 2014 Pivotal Software, Inc. All rights reserved.