Open Cloud Platform - Speaker Deck

Slide 1

Slide 1 text

© Copyright 2014 Pivotal. All rights reserved. © Copyright 2015 Pivotal. All rights reserved. Pivotal Cloud Foundry Open Cloud Platform for Software Innovation Sergiu Bodiu | Senior Solution Architect Asia Pacific & Japan

Slide 2

Slide 2 text

Slide 3

Slide 3 text

Slide 4

Slide 4 text

© 2014 Pivotal Software, Inc. All rights reserved. © Copyright 2014 Pivotal. All rights reserved. 4 Silicon Valley is coming…. We are going to work hard to make our services as seamless and competitive as theirs. “ ” -Jamie Dimon, CEO@JPMC, 2015 letter to shareholders

Slide 5

Slide 5 text

© Copyright 2015 Pivotal. All rights reserved. 5 Business Expectations Exceed IT Capabilities Cloud IT Technology Eras Mainframe Client-Server The exponential increase in business expectations is unsustainable for IT MILLIONS OF   APPS BILLIONS  OF USERS * Source: Gartner, 2013: “Hunting and Harvesting in a Digital World: The 2013 CIO Agenda” $ $ $ $ $ $ ABILITY OF IT TO DELIVER S/W STEADY IT BUDGETS* BUSINESS EXPECTATIONS

Slide 6

Slide 6 text

Slide 7

Slide 7 text

Slide 8

Slide 8 text

Slide 9

Slide 9 text

Slide 10

Slide 10 text

© Copyright 2015 Pivotal. All rights reserved. 10 Scaling Monolithic Architectures User Registration Catalog Orders Profile Search Recommendation Lists Account User Registration Catalog Orders Profile Search Recommendation Lists Account User Registration Catalog Orders Profile Search Recommendation Lists Account User Registration Catalog Orders Profile Search Recommendation Lists Account User Registration Catalog Orders Profile Search Recommendation Lists Account User Registration Catalog Orders Profile Search Recommendation Lists Account User Registration Catalog Orders Profile Search Recommendation Lists Account User Registration Catalog Orders Profile Search Recommendation Lists Account

Slide 11

Slide 11 text

Slide 12

Slide 12 text

© Copyright 2014 Pivotal. All rights reserved. 12 Monolithic Architectures • Complex • Modularity Dependent Upon Language / Frameworks • Change Cycles Tightly Coupled / Obstacle to Frequent Deploys • Inefficient Scaling • Can Be Intimidating to New Developers • Obstacle to Scaling Development • Requires Long-Term Commitment to Technical Stack

Slide 13

Slide 13 text

© Copyright 2015 Pivotal. All rights reserved. 13 Monolithic Architecture: Ripe for Disruption Scale of dev team / org User Adoption Monolithic µService (distributed) Redesign! Many apps start as monoliths ..and get redesigned when they start to achieve real success http://www.infoq.com/interviews/adrian-cockcroft-microservices-devops

Slide 14

Slide 14 text

Slide 15

Slide 15 text

Slide 16

Slide 16 text

Slide 17

Slide 17 text

© Copyright 2015 Pivotal. All rights reserved. 17 Steve Yegge’s Google Platform Rant “All teams will henceforth expose their data and functionality through service interfaces. Teams must communicate with each other through these interfaces. …There will be no other form of inter-process communication allowed: no direct linking, no direct reads of another team’s data store, no shared-memory model, no back-doors whatsoever. The only communication allowed is via service interface calls over the network. It doesn’t matter what technology they use. All service interfaces, without exception, must be designed from the ground up to be externalizable… That is to say, the team must plan and design to be able to expose the interface to developers in the outside world. No exceptions. Anyone who doesn’t do this will be fired. Thank you; have a nice day!“ Jeff Bezos CEO, Amazon Source: https://plus.google.com/+RipRowan/posts/eVeouesvaVX

Slide 18

Slide 18 text

© Copyright 2015 Pivotal. All rights reserved. 18 Organize Around Business Capabilities Data Access Service HTML JavaScript MVC Service UI Specialists Middleware Specialists DBAs Business Capability Business Capability Business Capability Siloed Functional Teams Siloed Application Architectures Cross- functional Teams Microservice Architectures http://martinfowler.com/articles/microservices.html#OrganizedAroundBusinessCapabilities

Slide 19

Slide 19 text

© Copyright 2015 Pivotal. All rights reserved. 19 We’ve trained IT to be paranoid & slow Project Mgmt UX Dev QA DBA Sys Admin Net Admin Storage Admin Adapted from: http://www.slideshare.net/adriancockcroft/goto-berlin MONOLITHIC DELIVERY

Slide 20

Slide 20 text

© Copyright 2015 Pivotal. All rights reserved. 20 So let’s re-train them… Product Mgr UX Dev QA DBA Sys Admin Net Admin Storage Admin BUSINESS CAPABILITY TEAMS USING MICROSERVICES PLATFORM OPERATIONS TEAM Adapted from: http://www.slideshare.net/adriancockcroft/goto-berlin

Slide 21

Slide 21 text

© Copyright 2015 Pivotal. All rights reserved. 21 Continuous Delivery Product Mgr UX Dev QA DBA Sys Admin Net Admin Storage Admin BUSINESS CAPABILITY TEAMS USING MICROSERVICES PLATFORM OPERATIONS TEAM Adapted from: http://www.slideshare.net/adriancockcroft/goto-berlin Self Service API

Slide 22

Slide 22 text

© Copyright 2015 Pivotal. All rights reserved. 22 INVENTORY Prod Release Prod Release Prod Release CATALOG Prod Release Prod Release Prod Release REVIEWS Prod Release Prod Release Prod Release SHIPPING Prod Release Prod Release Prod Release

Slide 23

Slide 23 text

Slide 24

Slide 24 text

© Copyright 2014 Pivotal. All rights reserved. 24 Microservice Architectures • Simple • Modularity Based on Component Services • Change Cycles Decoupled / Enable Frequent Deploys • Efficient Scaling • Individual Components Less Intimidating to New Developers • Enables Scaling of Development • Eliminates Long-Term Commitment to Technical Stack DEM O TIM E

Slide 25

Slide 25 text

Slide 26

Slide 26 text

Slide 27

Slide 27 text

© Copyright 2015 Pivotal. All rights reserved. 27 “We didn’t know test-driven development. We didn’t know CI/CD. We were excited […] a little skeptical […] but left becoming believers. What we didn’t realize was how ready we were for that change”

Slide 28

Slide 28 text

© Copyright 2015 Pivotal. All rights reserved. 28 “It wasn’t a natural journey […] to go and change everything we know about software. Cloud Foundry was paramount in our ability to lift the focus of what we’re doing to a completely different level.”

Slide 29

Slide 29 text

© Copyright 2015 Pivotal. All rights reserved. 29 “We felt like there was a 360-degree view that Pivotal brought to bear. This was more than just a technology transformation. It was a business transformation. It was about how we could deliver products faster. Cloud Foundry was a huge part of that.”

Slide 30

Slide 30 text

Slide 31

Slide 31 text

Slide 32

Slide 32 text

Slide 33

Slide 33 text

© Copyright 2014 Pivotal. All rights reserved. 33 Paying for your lunch… • Significant Operations Overhead • Substantial DevOps Skills Required • Implicit Interfaces • Duplication of Effort • Distributed System Complexity • Asynchronicity is Difficult! • Testability Challenges

Slide 34

Slide 34 text

© Copyright 2014 Pivotal. All rights reserved. 34 Significant Operations Overhead • Mitigate polyglot language/environment provisioning complexity via CF Buildpacks • Mitigate failover and resilience concerns via CF Scale, CF Health Monitor, and future CF App AZ’s (http://blog.gopivotal.com/cloud-foundry-pivotal/products/the-four-levels-of- ha-in-pivotal-cf) • Mitigate routing/load balancing and plumbing concerns via CF Router and CF Services • High quality monitoring = CF BP agent-based tooling, future CF metric streams • High quality operations infrastructure = CF BOSH! • Robust release/deployment automation = CF API, scriptable CF CLI, Maven/Gradle Plugins, Strong Cloudbees/Jenkins partnerships

Slide 35

Slide 35 text

© Copyright 2014 Pivotal. All rights reserved. 35 Substantial DevOps Skills Required • This is a Good Thing™ in any architecture! • CF keeps your microservices up and available (and your monoliths too!) • CF = development and production parity! • Polyglot persistence without all the fuss: CF BOSH and Service Brokers

Slide 36

Slide 36 text

© Copyright 2014 Pivotal. All rights reserved. 36 Distributed System Complexity • Agreed: Microservices imply distributed systems. • All of the CF platform features we’ve discussed help to mitigate these concerns: • latent/unreliable networks • fault tolerance • load variability

Slide 37

Slide 37 text

© Copyright 2014 Pivotal. All rights reserved. 37 Testability Challenges • With CF, it is NOT difficult to recreate environments in a consistent way for either manual or automated testing! • Idiomatic Microservices involves placing less emphasis on testing and more on monitoring • Not sure where this idea comes from… • CF is an enabler of both!

Slide 38

Slide 38 text

© Copyright 2015 Pivotal. All rights reserved. 38 Source: “Microservice Prerequisites,” Martin Fowler, August 2014. https://www.flickr.com/photos/gusset/3723961589 You must be this tall to use Microservices… • Rapid provisioning • Basic monitoring • Rapid application deployment • DevOps culture

Slide 39

Slide 39 text

Slide 40

Slide 40 text

© Copyright 2014 Pivotal. All rights reserved. 40 The build is not done until a customer is using it. •The business goal is to learn your way to do a better product that establishes competitive advantage, leading to profit.

Slide 41

Slide 41 text

Slide 42

Slide 42 text

© Copyright 2015 Pivotal. All rights reserved. 42 I. Codebase II. Dependencies III. Configuration IV. Backing services V. Build, release, run VI. Process VII. Port binding VIII. Concurrency IX. Disposability X. Dev/Prod parity XI. Logs XII. Admin Process http://12factor.net 12 Factor Apps

Slide 43

Slide 43 text

© Copyright 2015 Pivotal. All rights reserved. 43 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 http://12factor.net

Slide 44

Slide 44 text

© Copyright 2015 Pivotal. All rights reserved. 44 The Cloud Platform Evolution TRADITIONAL IAAS Virtualization Platform Operating System Data base Web Server Mess aging Your Application Code Physical Servers Data base Web Server Mess aging Your Application Code IAAS Your Application Code PAAS IAAS PAAS

Slide 45

Slide 45 text

Slide 46

Slide 46 text

© Copyright 2015 Pivotal. All rights reserved. 46 Capabilities at a Glance Containers and Orchestration Log Aggregation Dev/Ops Metrics Services: Data, Mobile, Platform High Availability and Scaling Network Isolation, Security Groups Automatic Middleware Configuration Simple  Service Binding Automatic IaaS Provisioning Roles and Policy Management

Slide 47

Slide 47 text

© Copyright 2015 Pivotal. All rights reserved. 47 Enable DevOps culture BUILD  APPLICATION • Auto-detect frameworks • Link to PaaS • Self-service deploy • Dynamic routing • Elastic scale • Integrated HA • Autoscaling and APM • Log aggregation • Policy and Auth • A/B versioning • Live upgrades • Self-service   removal PUSH FIRST RELEASE MAINTAIN APPLICATION UPDATE APPLICATION RETIRE APPLICATION

Slide 48

Slide 48 text

Slide 49

Slide 49 text

© Copyright 2015 Pivotal. All rights reserved. 49 Continuous Delivery with Pivotal CF High Quality Software, Faster, From Idea to Production SPEED Releasing smaller things more often will reduce complexity and improve time-to-market QUALITY We embed testing early in the lifecycle to surface problems sooner, avoiding last minute issues and helping us be more responsive to change AGILITY Let’s push updates on a regular basis without ANY downtime to improve customer experience and shorten time-to-market AUTOMATION Let’s integrate tools and automate processes from testing, to builds & deployment Automated Build + Quality Check (Unit Test, Static Code Analysis etc.) Store Environment Agnostic Build Artifacts Commit Code Change Automated Integration Testing Automated + Manual Testing (Acceptance, Performance, Load) Zero Downtime Upgrades Pipeline Operations Tool Chain Auto Auto Auto Auto OR Manual Auto OR Manual TEST + UAT + STAGING DEV PROD GitHub Jenkins

Slide 50

Slide 50 text

Slide 51

Slide 51 text

© Copyright 2015 Pivotal. All rights reserved. 51 Infrastructure Applications Monoliths Microservices Pivotal CF Continuous Delivery Software Factories Feedback Rapid Iteration Horizontal Scale Diversity of Clients Physical/Virtual Goals & Needs Supporting Changes

Slide 52

Slide 52 text

© Copyright 2015 Pivotal. All rights reserved. 52 The Digital Innovation Center OPTIMIZED FACILITIES AGILE ORGANIZATION MEASURED SUCCESS INITIALLY CO-LOCATED WITH PIVOTAL LABS; TRANSITIONED TO A DESIGNATED TDA SITE THE BEST TALENT FOCUSED ON DIGITAL PRODUCTS THAT MOVE BUSINESS FORWARD OFTEN DRIVEN AS A SEPARATE BUSINESS; GOALED ON ACCELERATED CAPABILITY DELIVERY EXISTING, INTEGRATED SYSTEMS / YOUR IAAS CLOUD(s) /

Slide 53

Slide 53 text

© Copyright 2015 Pivotal. All rights reserved. 53 Building an Innovation Center with Pivotal Market your mission. Architect new org model(s) and enable leadership with tools. • Scope and Alignment • Clear Measurement • Communication Planning • Org Definition • Training, Coaching and Mentoring A talent strategy that pulls the best internal and external people into an innovation center. • Interviewing and Selection Framework • Pivotal Recruiting Support and Pairing • Candidate Onboarding • Employee Training Guidance Incubate in our shop. Transition to your location(s) of choice as maturity grows. • Facilities Planning • Integration with existing IT assets • Leadership Mentoring • Ongoing Pivotal Support Reduction as TDA Maturity Grows LOCATION TALENT STRATEGY INITIALLY CO-LOCATED AT PIVOTAL AND THEN TRANSITIONED TO YOUR FACILITY

Slide 54

Slide 54 text

© Copyright 2015 Pivotal. All rights reserved. 54 Paired Delivery DESIGNER PRODUCT OWNER DEVELOPERS (2-3 PAIRS) ATOMIC TEAMS • Responsible for an app, service or capability from end-to-end • Generally sized as “2 pizza” teams • Developers work in “pairs”; two people with one keyboard • Supported by Agile Ops • Identify a small set of business-relevant applications • Begin to transition apps to the paired delivery model • Staff the paired teams with our and your people • Go end-to-end using the people, tech and process • Identify best practices and models while doing work • Decrease Pivotal engineers as your maturity grows • Gradually transition into new model in Year 1 and 2

Slide 55

Slide 55 text

© Copyright 2014 Pivotal. All rights reserved. 55 What Does Agile Operations Mean? • Release smaller things more often • Reduce the number of manual / people “touches” • Use PaaS and containers to standardize on fewer tools • Move away from tickets and automate release management • Shift more testing into the Developer’s realm • Invert your testing pyramid and automate as much as possible • Log everything and use tools to make sense of it all • Enable Operations and QA as a job functions within “One team”

Slide 56

Slide 56 text

© Copyright 2015 Pivotal. All rights reserved. INFRASTRUCTURE SITE RELIABILITY PLATFORM Notional Model Agile Operations 56 Innovation; Plan, design, develop and test business capabilities as deployable artifacts Production Apps; config, deployment, QA, monitoring, scaling App Platform; upgrade PCF, capacity planning, service mgmt., scale platform Infra Platform; Rack and stack, networking, data storage, etc. ROLES Cross-Functional   (Prod. Owner, Dev, QA) Application Operators Platform Operators Engineering (Storage, Security, Network, etc.) AREAS OF FOCUS BUSINESS CAPABILITY

Slide 57

Slide 57 text

© Copyright 2015 Pivotal. All rights reserved. 57 Another Org Model View BUSINESS CAPABILITY TEAMS INFRASTRUCTURE SITE RELIABILITY AGILE OPERATIONS SHARED SERVICES PLATFORM ENGINEERING PRODUCTION PAAS AND UNDERLYING TECHNOLOGY STACKS / SERVICES NON-PROD PAAS AND RELATED STACKS / SERVICES SERVICE OWNER EXPLORATORY TESTING PROD DEPLOYS APPS UP- TIME SERVICE OWNER PCF ENGINEERS CONTINUOUS DELIVERY PIPELINE (TESTING, BUILD AND RELEASE AUTOMATION) SERVICE OWNER? ENG’S THAT MATRIX INTO BROADER ORG PRODUCT OWNER DESIGNER 2-3 DEV PAIRS TESTER(S)

Slide 58

Slide 58 text

© Copyright 2015 Pivotal. All rights reserved. 58 Invert Your Testing Pyramid Manual Verification Automated End-End UI Integration Unit Verifying– Asserting the system produces the expected outcome Complexity  Maintainability, Cost Low High • Slow & fragile • No pinpoint failure indication Auto. UI Automated API/ Workflow Automated Integration Automated Component Automated Unit Manual Exploratory Testing • Increased speed, decreased maintenance • Pinpoint failure indication Testing – Probing the system when you don’t know how it will respond Performance Test  any or all of these  layers as needed

Slide 59

Slide 59 text

© Copyright 2015 Pivotal. All rights reserved. 59 What End to End Could Look Like GUI API/Flow Integration Component Unit DEV STUBBED INT PRE-PROD PROD Interfaces Data INTERNAL EXTERNAL CFG CFG CFG CFG CFG Build / Deploy / Orchestrate Commit environment specific configurations Run a subsets of tests to isolate parts of the system Do not need to run all tests in all environments Performance, Security Exploratory tests in any environment Isolate and test portions of the system

Slide 60

Slide 60 text

© Copyright 2015 Pivotal. All rights reserved. 60 What is Spring? #1 Enterprise Java App Dev Framework • OSS, Apache 2.0 licensed • Proven, mature, since 2004 • Well understood and documented • Millions of downloads • Used heavily by Netflix and F2000

Slide 61

Slide 61 text

© Copyright 2015 Pivotal. All rights reserved. 61 Spring IO Foundation Modular, embeddable developer libraries • Security – LDAP, OAUTH2, Kerberos • Integration/Batch/Messaging/Caching • SOAP Web services, REST, HATEOAS • Data Access (noSQL, RDBMS, Search) • Rich OAUTH2 binding ecosystem • Mobile, Web Apps Application and microservice patterns

Slide 62

Slide 62 text

© Copyright 2015 Pivotal. All rights reserved. 62 Spring IO Execution: Spring Boot application configuration patterns • Convention-over-configuration, no XML, no code generation • Autoconfigure, embed servlet engine • Get out of the way quickly if you want to change defaults • Provide production ready features • Service Binding for Cloud Foundry • Java, Spring, Groovy

Slide 63

Slide 63 text

© Copyright 2014 Pivotal. All rights reserved. 63 Spring IO Execution: Spring Cloud • Runtimes and their client libraries for: – Service Discovery – Configuration Management – Circuit Breakers – Intelligent Client Side Routing – Reverse Proxies – ….and much more • Security (encrypt, SSO, roles) • Connectors for CF, Heroku, AWS application coordination patterns

Slide 64

Slide 64 text

Slide 65

Slide 65 text

© Copyright 2014 Pivotal. All rights reserved. 65 Twelve Factor + Microservices • Fully compatible architectural style • Frameworks tend to optimize around same ideas • Spring Boot + Cloud • http://projects.spring.io/spring-boot • http://projects.spring.io/spring-cloud • Dropwizard (https://dropwizard.github.io/dropwizard)

Slide 66

Slide 66 text

Slide 67

Slide 67 text

© Copyright 2015 Pivotal. All rights reserved. 67 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

Slide 68

Slide 68 text

Slide 69

Slide 69 text

© Copyright 2015 Pivotal. All rights reserved. 69 Infrastructure Automation Platform Runtime Application Framework BOSH External Backing Services Cloud Native Platform Build Pipeline: CI, CD, Version control Microservices are key for Cloud Native Java Cloud Native App Integration contracts

Slide 70

Slide 70 text

© Copyright 2015 Pivotal. All rights reserved. 70 12 factor apps & Microservices Container Orchestration Infrastructure Automation Polyglot buildpacks & Spring Cloud Elastic Runtime/Diego BOSH Cloud Native Application Frameworks Cloud Native Runtime Platform Cloud Native Operations Cloud Native Culture A cloud native platform is composed of three layers, that span & support the entire life-cycle of an application from development to production

Slide 71

Slide 71 text

© Copyright 2015 Pivotal. All rights reserved. 71 Empowered Culture Infrastructure Automation Runtime Platform Cloud Native Application Framework 12 factor app Spring Cloud Services Microservices Polyglot Java, Ruby, Python, Node, PHP, Go XII

Slide 72

Slide 72 text

Slide 73

Slide 73 text

Slide 74

Slide 74 text

© Copyright 2015 Pivotal. All rights reserved. 74 Principles > Practices > Tools Infrastructure Automation Runtime Platform Cloud Native Empowered Culture Collaborative High Trust Outcomes Application Framework

Slide 75

Slide 75 text

Slide 76

Slide 76 text

Slide 77

Slide 77 text

A NEW PLATFORM FOR A NEW ERA Thank You sbodiu@pivotal.io