Cloud Native Architecture Transforming how world builds software Sergiu Bodiu Platform Architecture

My Personal Journey meetup.com/singasug sergiu@pivotal.io

© Copyright 2016 Pivotal. All rights reserved. Lessons Learned ● Break Big Things Into Small Chunks
 Worked Incrementally ● Detailed Multi-Year Roadmaps Rarely Become Reality ● Keep Your Feedback Cycle as Short as Possible ● Automate Everything You Can (TDD, CI/CD) ● Build New Skills Through Pairing and By Doing ● Experimentation Informs Strategy ● Start With “One Thing”

How Big Company IT delivers software

No content

No content

7 Agile IT Organization Design: For Digital Transformation and Continuous Delivery - Sriram Narayan

8 Agile IT Organization Design: For Digital Transformation and Continuous Delivery - Sriram Narayan

Agile IT Organization Design: For Digital Transformation and Continuous Delivery - Sriram Narayan

Q: How much value do you get from the code that is written, but is not deployed?

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.

© Copyright 2015 Pivotal. All rights reserved. Confidential. 12 What is it? What’s unique about it?

Pivotal Confidential 13 6. Pivotal Cloud Foundry Enriches the Platform Elastic Runtime Cloud Native Microservices In
 Containers Others CI Service (Jenkins, Concourse) Google Pivotal Ops Manager MySQL vSphere Amazon OpenStack Benefit: Easy to start, multiple skill levels, peace of mind, and Pivotal 24/7 support Pivotal Network distributes cross-cloud 
 runtime & service brokers with full integration testing & CVE patch coverage vCloud Azure Service Broker Marketplace Mobile
 Services Redis, Rabbit MQ UI to manage applications, service broker dashboards, usage reporting Cloud Foundry API Cloud Foundry BOSH Pivotal Apps Manager Pivotal Network One click cluster install, patch, upgrade

Platform Operations 14

15 Networking Admin Storage Amin Sys Admin IaaS Admin App Architect Security Auditor QA Perf Test Platform Champion Project
 Manager Platform Operations Team Platform Operations for Cloud Foundry

Cloud Native 16

Cloud Computing Containers Agile DevOps Platform Operations Microservices Cloud Native Principles | Misconceptions | Value Proposition 17

Defining Cloud Native Cloud native is a term describing software designed to run and scale reliably and predictably on top of potentially unreliable cloud based infrastructure.

Business'Value,'Agility'&' Cost'Savings' Traditional IT Storage Servers Networking O/S Middleware Virtualization Data Applications Runtime You Manage O/S IaaS Storage Servers Networking Middleware Virtualization Data Applications Runtime You Manage IaaS O/S Cloud Native Storage Servers Networking Middleware Virtualization Data Applications Runtime Pivotal CF + Choice of IaaS You Manage Platform Evolution 19

images from http://1staeronchair.co.uk/wp-content/uploads/2014/07/specs-image.jpg and http://www.sit4life.com/product-images/12/93/original/17737.jpg

OS embedded Google AWS Azure VMW Openstack CPI Container Orchestration Cloud Orchestration Tracing Metrics API/ID Data Flow ETL Integration Stream/Event Model Java Microservices Spring Boot Spring Cloud Netflix OSS .Net Microservices with Spring Cloud CI Pivotal Labs PWS 40k 1 PCF 4 Ops people Value Line 21

Pivotal Confidential 22 The Cloud Foundry Difference • Rapid developer responsiveness to change, balancing safety – Don’t spend time & risk maintaining custom containers and build pipelines • Freedom of deployment options – same experience, any cloud • Open community extension & innovation – Submit a PR, sign the CLA, if it passes CI it likely will be accepted – Cloud Foundry Dojo – gain committer access through 6 weeks of immersion with Pivotal R&D • Strong “Day 2” operations – no mystery as to “how will I run this thing?” • Structured platform – pre-integration & testing simplifies your toolchain

“Think of a product on a Monday and deliver on Friday.”

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

25 http://www.slideshare.net/GETurkiye/predix-cloud

An idea in the morning, is running in production by evening https://www.wealthfront.com/engineering Can you release new features to your customers every week?

Introduction to Spring Boot and Spring Cloud Services

28 Cloud Native Framework Application Framework Runtime Platform Infrastructure Automation Infrastructure Culture Dev Dev IT Ops IT Ops IT Ops Tools Spring Cloud Spring Boot BOSH.IO AWS VMWare OpenStack Azure

29 Spring Cloud Spring Boot Dev Spring Boot From 0 to app in < 5 min Enterprise Java with dynamic language productivity Spring Cloud Designed for fragile infrastructure in partnership with Netflix Java Microservice Framework 100% Spring Boot enabled Application Framework

30 Spring Boot is an opinionated framework to simplify bootstrapping and development of new Spring Applications What is Spring Boot?

31 Spring Boot Dynamic language productivity with maturity of enterprise Java Cloud Native: Direct support for Microservices, NetflixOSS++ Fully automated app server configuration and deployment Production ready Ops metrics out of the box, with a switch

Spring Boot Adoption
 Source: oss.sonatype.org 3.66M Monthly Maven downloads 8.8M

Cloud Foundry Service Broker / BOSH release • NetflixOSS as native PCF services Simple install and configure for NetflixOSS (and more) • Reduce setup time and cost Simple to operate, upgrade with zero downtime • PCF managed = dramatically lower ops requirement Security: OAUTH2, HTTPS, PCF UAA integration, Role based access control Spring Cloud Services for Pivotal Cloud Foundry NetflixOSS-as-a-service in Pivotal Cloud Foundry

Spring Cloud Services for Pivotal Cloud Foundry • Install • Config • Manage • Secure Spring Cloud Services Config Server Service Registry Circuit Breaker Dashboard

No content

© Copyright 2015 Pivotal. All rights reserved. 36 How many microservices? ELEVEN

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

No content

39 Software is eating the world

Platform Architect
 Asia Pacific & Japan Singapore Spring User
 Group DevOpsDays Singapore
 Conference

© Copyright 2016 Pivotal. All rights reserved. Lessons Learned ● Detailed Multi-Year Roadmaps Rarely Become Reality ● Break Big Things Into Small Chunks
 Worked Incrementally ● Keep Your Feedback Cycle as Short as Possible ● Automate Everything You Can (TDD, CI/CD) ● Build New Skills Through Pairing and By Doing ● Experimentation Informs Strategy ● Start With “One Thing”

Let’s build something
 MEANINGFUL