Cloud-Native Roadshow Boston

pivotal.io/roadshow #cnr

Cloud-Native RoadshowBoston


Pivotal

“Our Mission is to transform how the world builds software.”


Cameron Stewart @cws322

Casey West @caseywest


Yes


Will I get a copy of these materials?

Yes


Jamie Dimon, CEO JPMC Source: JPMC Annual Shareholder Letter (2015)

“Silicon Valley is coming… and they want to eat our lunch.”


Casey West

“We’re from Silicon Valley. We brought lunch.”


The Pivotal Cloud Foundry Ecosystem

Pivotal Google Cloud


Google Cloud

Team Google

Cloud Marketing Software EngineerSoftware Engineer

Meaghan Kjelland

Solutions Stuff

Jay MarshallNicole Rogers Colleen Briant

pivotal.io/roadshow #cnrCopyright*Solace

o Open*protocol2basedo Hybrid*cloud*readyo Proven


Pivotal + New Relic = Go Faster & See More Clearly

✓  SSAE-16/SOC II New Relic Platform ✓  SSAE-16/SOC II Data Center ✓  CSA-STAR

Browser Mobile

Server (Virtual) Hardware

Server OS

Application & Application Microservices

PCF Nozzle

Application Agent

newrelic.com/pivotal


The Cloud Foundry Ecosystem


What is Cloud-Native?


Cloud-Native is


• Composable Architectures

Cloud-Native is



• Automated Process

Cloud-Native is




• Collaborative Culture

Cloud-Native is




• Collaborative Culture

• Structured Platform

Cloud-Native is


Architecture Process Culture Platform



• Microservices



• Microservices

• Functions as a Service a.k.a. “serverless”



• Microservices


• Migration from Monolith to µServices



• Microservices


• Migration from Monolith to µServices

• Spring Boot


Your architecture plays a key role in your operational maturity.






• Test Driven Development




• Continuous Delivery




• Continuous Delivery

• Automated Software Delivery Life Cycle (SDLC)



Automate integration tests.



Automate the path to production.



Increase velocity and reduce risk with frequent, small batch sizes.





Choose architectures that are less likely to resist automation.





• Devops



• Devops

• C.A.L.M.S.



• Devops

• C.A.L.M.S.

• Site Reliability Engineering (SRE)



• Devops

• C.A.L.M.S.

• Site Reliability Engineering (SRE)

• Customer Reliability Engineering (CRE)



Kelsey Hightower, Google

“Devops is group therapy for inefficient tools.”


Architecture Process Culture Platform• Collaboration

• Automation

• Learning

• Measuring

• Sharing



Ben Treynor, Founder of Google’s Site Reliability Team

“Site Reliability Engineering is what happens when you ask a software engineer to design an operations function.”



Dave Rensin, Director of Google Customer Reliability Engineering

“Customer Reliability Engineering’s mission is to create a shared operational fate between Google and our Google Cloud Platform customers.”





• Minimum Viable Platform




• Infrastructure Integration





• Service Integration





• Service Integration

• Polyglot


Architecture Process Culture Platform• Dynamic DNS, routing, and load balancing

• Automated service discovery and brokering

• Infrastructure automation

• Health management, monitoring, and recovery

• Immutable artifact repository

• Log aggregation



Pivotal Cloud Foundry Elastic Runtime




Pivotal Cloud Foundry Operations Manager




Pivotal Cloud Foundry Operations ManagerBOSH Release





Spring Boot and Spring Cloud Services

BOSH Release






BOSH Release

12 Factor






BOSH Release

12 Factor






Cloud Provider Interface (CPI)

BOSH Release

12 Factor







BOSH Release

12 Factor







BOSH Release

12 Factor







BOSH Release

12 Factor







BOSH Release

12 Factor







BOSH Release

12 Factor







BOSH Release

12 Factor

Programmable compute, storage & networking







BOSH Release

12 Factor

Programmable compute, storage & networking







BOSH Release

12 Factor

Programmable Infrastructure







BOSH Release

12 Factor








BOSH Release

12 Factor

• Apigee • Cloud Storage • BigQuery • PubSub • Cloud SQL • Machine Learning APIs • Bigtable • Spanner • Stackdriver


Java, .Net, Static, Node, Python, Go, PHP, Ruby, Binary



Production should keep promises about resiliency, repeatability, and reliability.


The Evolution of Cloud-Native

AgileConfig Mgmt

TDD12 Factor



AgileConfig Mgmt

TDD12 Factor

µServicesDevopsCI/CD

Platforms



AgileConfig Mgmt

TDD12 Factor

µServicesDevopsCI/CD

Platforms

ObservabilitySLI/SLOReliabilityAvailability


Verma et al, “Large-scale cluster management at Google with Borg”

“Almost every task run under Borg contains a built-in HTTP server that publishes information about the health of the task and thousands of performance metrics (e.g., RPC latencies).”

Observability


Spring Boot Actuator – Health$ curl -s http://my-app/health | jq { "status": "UP", "diskSpace": { "status": "UP", "total": 1056858112, "free": 907612160, "threshold": 10485760 } }


Spring Boot Actuator – Metrics$ curl -s http://my-app/metrics | jq { "mem": 734352, "mem.free": 459292, "processors": 4, "instance.uptime": 17072859, "uptime": 17078694, "systemload.average": 0.6, "heap.committed": 664064, . . .


Service Level Indicators are data about the operational characteristics of a service.

SLIs


Service Level Objectives set reliability expectations based on SLIs.

SLOs


If a system should be 99.99% available then it can be 0.01% unavailable.

If we have error budget left development can take risks. If not we have to fix it.

SLAs – Error Budgets


Minimize the amount of errors so we can launch code as fast as possible.

Error Budgets – Aligned Incentives


Service Level Objective: 99.99% of requests return under 50ms.

The error budget allows for 0.01% of requests to exceed the SLO.

Error Budgets – Latency


Service Reliability Hierarchy

Monitoring

Incident Response

Post Mortem / Root Cause Analysis

Testing / Release Procedure

Capacity Planning

Development

Product



Monitoring

Incident Response



Capacity Planning

Development

Product



Monitoring

Incident Response



Capacity Planning

Development

Product



Monitoring

Incident Response



Capacity Planning

Development

Product



Monitoring

Incident Response



Capacity Planning

Development

Product



Monitoring

Incident Response



Capacity Planning

Development

Product



Monitoring

Incident Response



Capacity Planning

Development

Product



Monitoring

Incident Response



Capacity Planning

Development

Product


John Allspaw

“Ways in which things go right are special cases of the ways in which things go wrong.”


Susan J. Fowler, “Production-Ready Microservices”

“Every µService at Uber should be stable, reliable, scalable, fault tolerant, performant, monitored, documented, and prepared for any catastrophe.”


A distributed system cannot simultaneously have consistent views of the data at each node and availability of the data at each node if the network becomes partitioned.

The CAP Theorem


A distributed system cannot simultaneously have consistent views of the data at each node and availability of the data at each node if the network becomes partitioned.

The CAP Theorem


and availability of the data at each node if the network becomes partitioned.

The CAP Theorem

A distributed system cannot simultaneously have consistent views of the data at each node


and availability of the data at each node if the

network becomes partitioned.

The CAP TheoremA distributed system cannot simultaneously

have consistent views of the data at each node






Requests aren’t

being served!






Requests aren’t

being served!Unavailable!











Serving requests

like normal!






Serving requests

like normal!Inconsistent!


Raymond Blum and Rhandeev Singh, “Site Reliability Engineering”

“Data integrity is a function of availability of a given entity over its lifetime. This is analogous to system uptime and even more critical.”



“Data availability must be a foremost concern of any data-centric system.”



“From the user’s point of view, data integrity without expected and regular data availability is effectively the same as having no data at all.”


Availability is a User Experience problem.


Building software like SRE—with a focus on observability, reliability, and availability—makes you cloud-native.


Ready?


github.com/cwest/storage-demo

http://github.com/cwest/storage-demo



Cloud-Native Roadshow Closing


Wikipedia Article “Operability”

“Operability is the ability to keep an equipment, a system, or a whole industrial installation in a safe and reliable functioning condition, according to pre-defined operational requirements.”

What is operability?


Kenny Bastani, Pivotal

“A microservice is an application small enough that an engineer new to the source code can reason about it in a day or less.”

Microservice


The ability to deploy to production whenever the organization chooses without anyone setting themselves on fire.

Continuous Delivery


Engineer your operations.

SRE Culture


It doesn’t matter how beautiful your architecture is, how easy deployment is, or how great your culture is if production is a tire fire.

Pivotal Cloud Foundry


No CEO Ever

“I appreciate the progress you made on not delivering anything.”

Undifferentiated Heavy Lifting


Unique Business Value is the tools, systems, and processes which improve the unique value your organization provides.

The only thing that matters


Acacio Cruz and Ashish Bhambhani, “Site Reliability Engineering”

“Provide product development with a platform of SRE-validated infrastructure, upon which thy can build their systems. This platform will have the double benefit of being both reliable and scalable.”


PCF is the first platform in CRE review.


Ben Treynor, Founder of Google’s Site Reliability Team

“The SRE Benediction: May the Queries Flow, And the Pagers Remain Silent”


Cameron Stewart @cws322

Casey West @caseywest


The Pivotal Cloud Foundry Ecosystem

Pivotal Google Cloud


You are all cloud-native now.


You learned how to deliver software like Pivotal and Google.

Read for free: landing.google.com/sre/book.html

Save $100 on registration with code S1P_EVENT_CNR100

Technology

Cloud-Native Roadshow Boston