Embed Size (px)
Citation preview
1© Copyright 2015 Pivotal. All rights reserved. 1© Copyright 2015 Pivotal. All rights reserved.
The Cloud Native Journey:Greenfield@cote, July 2015
2© Copyright 2015 Pivotal. All rights reserved.
“We are uncovering better ways of developing software by doing it and
helping others do it.”Source: The Agile Manifesto, 2001.
3© Copyright 2015 Pivotal. All rights reserved.
We are tracking three types of cloud native “journeys”
1. Greenfield – the freedom to start from scratch
2. Transformation – taking on the task of changing how you develop, company/dept. wide
3. Legacy – rewriting or quarantining existing, “old” applications
4© Copyright 2015 Pivotal. All rights reserved.
Greenfield goals – bootstrap in 1-4 weeks Be successful, build trust – if you fail at the simplest task, you will be
given little chance to succeed at the harder ones
Build a software delivery pipeline that can deploy small batches
Deliver an application that has small, but meaningful customer value
Reduce full cycle time to a day, which relies on:– Known process that performs hypothesis/deploy/validate loop– Strict, automated testing– Continuous Integration/Delivery– Automated, self-service infrastructure Cloud Platform
5© Copyright 2015 Pivotal. All rights reserved. 5© Copyright 2014 Pivotal. All rights reserved.
Greenfield Example
6© Copyright 2015 Pivotal. All rights reserved.
Example: SafeMeds executable RFQ timeline
Source: Pivotal GSA Response Addendum, July 2015, also, see more in the project scrap book.
Day 1
- Create dev & prod environments
- Code & deploy search story, pulling data from FDA API
- User research, persona creation
- Identify initial user tasks to deliver
Day 2
- Refine requirements- Wireframes- Rewrite search (API
throttling hampers autocomplete)
- Create user stories
Day 3
- Mobile design- Fix & deploy bugs in
search- Usability testing with
2 real users- Code & Deploy drug
interaction feature- Start on auto-
complete
Days 5-8
- Standup- Paired coding- Design- Usability testing- Feature prioritization- Backlog management- Retro
Day 4
- Team ideates 90 ideas down to 8
- Create validation criteria
- More API workaround for autocomplete
Finished!
Boot-strapping Steady-state
Process & tools that enabled deploying to production every day
7© Copyright 2015 Pivotal. All rights reserved. 7© Copyright 2015 Pivotal. All rights reserved.
Greenfield Practices
8© Copyright 2015 Pivotal. All rights reserved.
Achieve the business goal of faster releases by revisit your product design process Deploy to
production each time, avoid waterscrumfall
Relies on:– Product
approach– Small batch
oriented pipeline and process
– Cloud native automation
Inception
Hypothesize
Validate w/real use(r)s
Did it work?
9© Copyright 2015 Pivotal. All rights reserved.
Create your new pipeline by establishing a continuous delivery pipeline
Build Test/Verify Package repository
VersionControl
InfrastructurePlatform
(IaaS, PaaS, VMs)
ProductionConcerns
(monitoring, scaling, etc.)
Feedback Loop
Specify Code
10© Copyright 2015 Pivotal. All rights reserved.
Get familiar with everyday cloud native tools and practices Strict daily meeting cadence
Integrated team: strong connection to development, product management, design, users
Open project management (Tracker, etc.)
CI/CD, dev automation
12 factor apps
Monoliths & microservices
Cloud native platform
The process is an important “tool”!
Tools that support the process
11© Copyright 2015 Pivotal. All rights reserved.
Use 12 factor app principles to create cloud ready applications
A set of best practices for developing and deploying cloud-native software.
Practices translate into platform features and workflow requirements.
Codebase Dependencies Config Backing Services
Build, Release,
RunProcesses Port
BindingConcurrenc
y
DisposabilityDev/Prod
Parity Logs Admin Processes
Source: “The Twelve-Factor App,” “The Agility Frontier - Continuous Delivery and Pivotal Cloud Foundry,” July 2015.
12© Copyright 2015 Pivotal. All rights reserved.
Further cloud native architecture guidance
Architectural considerations for continuous delivery, container, & microservices driven approach to cloud native app dev & delivery
Overview of common cloud native patterns such as circuit breakers, registries, anti-corruption layer, API gateways, configuration practices, etc.
Free, and just 51 pages
Get the PDF here.
13© Copyright 2015 Pivotal. All rights reserved.
A cloud platform enables continuous delivery speed by standardizing and automating as much as possible
14© Copyright 2015 Pivotal. All rights reserved.
After the greenfield, next steps to transformingMedium Term (1-2 quarters): Larger projects: greenfield or moribund app
Metrics: cycle time, MTTR, costs/staff, revenue/biz goals
New services as microservices
Document your success, educate from “failures”
Longer Term: Establish company-wide, self-service cloud platform
Supportability- Creating standard project templates, blue prints, consistency
Fully enable multi-cloud
Training & education Internal summits and hackathons
Strangle old services into microservices
15© Copyright 2015 Pivotal. All rights reserved. 15© Copyright 2015 Pivotal. All rights reserved.
Thanks!@cote | [email protected]
