cloud coding, or, starting an it strategy to become a software defined business
TRANSCRIPT
11
Cloud coding
Or, What does IT need to start doing to become a software defined business?
30 June 2015@cote | [email protected]
Slides: http://cote.io/cloud-coding
2
Conclusions
When you know you need to change – the business is freaking out
“Cloud” for developers is about a new way of: – Doing product design & management– Design & development of code– How code is run & managed in production
Next steps: – Get continuous delivery– Learn cloud-native architecture– Get a cloud platform
3
@cote – Director, Technical Marketing at Pivotal for Pivotal Cloud Foundry
Former industry analyst at 451 Research and RedMonk
Corporate Strategy & M&A at Dell
Former software developer
More: http://cote.io or [email protected]
Hello!
44
Pardon the biz talk(It will be brief)
55
“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
Source: 2015 letter to shareholders.
6
Software is changing Industries
$3.5B valuationFinancial Services
$3.5B valuationTravel & Hospitality
$19B valuation Transportation
$3.2B Acquisition by GoogleHome Automation
$20B valuation Entertainment
$1.1B acquisition Monsanto--Agriculture
7
Changing is hard, often impossible
Source: “Creative destruction in the S&P500 index,” Jan 2014.
8
Unless the business is freaking out, you won’t find enough support for big, technical change(for the most part)
• Changing how you use technology will be hard to impossible, you will need executive sponsorship
• Avoid “technology for technologies’ sake”
• How does new tech make the business run better, or enable new business models?
Theory of when to change your IT strategy
99
Cloud?
1010© Copyright 2015 Pivotal. All rights reserved.Columbus Renaissance hotel, 3rd floor. See also Plumbing: Design and Installation.
11
Failure to change the operational model
31%
Doing too little19%Failure to change the fund-
ing model13%
Defending I&O and doing too much
11%
Focusing on the wrong benefits
10%
Using the wrong tech-nologies
6%
Nothing is wrong - It's great!
5%
Something else5%
"What is going wrong with your private cloud?"
Sources: “Problems Encountered by 95% of Private Clouds,” Gartner, Feb 2015. See also 451 commentary on cloud for net-new applications and survey data on cloud pain points.
It’s not enough to just get a blinking cursor
1212
Cloud for software defined businesses
13
You are either building a software business…
Or losing to someone who is.
- @littleidea
Source: Andrew Shafer, July 2013.
14
Use cloud to enable three key IT strategies
End Goal - Continuous delivery & DevOps to focus on better design, development, and throughput of custom written software
How - Cloud-native architecture and coding
Enablement - A Cloud platform to support all of the above and provide the production runtime
1515
Continuous Delivery & DevOps
16
The overall goal: continuous delivery
Build Test/VerifyPackage repository
VersionControl
InfrastructurePlatform
(IaaS, PaaS, VMs)
ProductionConcerns
(monitoring, scaling, etc.)
Feedback Loop
Specify Code
Development CI/CD Ops
17
Goals that lead to DevOps
1. Delivering software that runs on the Internet (mobile, web, etc.)
2. The pipeline is the factory, from concept, to code, to production
3. Faster turns, while maintaining quality, uptime, performance– Lean approach to entire process– Shorten time to customer value– Keep the site up, resilience vs. failure
Consequence: requires Development & Operations to combine
Sources: see The Practice of Cloud System Administration, chapter 8; Damon Edward's 2012 piece "Use DevOps to Turn IT into a Strategic Weapon”; The Phoenix Project for DevOps a la The Goal. See also John’s Willis’ DevOpsDays Paris talk more technical-based drivers.
18
Sources: “Getting Your Arms Around DevOps – DevOps Patterns and Practices,” Cameron Haight, Gartner, Oct 2014.
1919
Cloud-native Applications
20
12 factor apps – thriving in a cloud world
• How to code at “cloud speed”
• Distributed application design principals
• ALM principals
• Emphasis on stateless
• DevOps-minded principals
Source: 12factor.net.
21
Microservice enable cloud-native applications
More details: “Microservices,” by Lewis and Fowler.
22
Further reading…
Source: Migrating to Cloud-Native Application Architectures, Matt Stine, 2015. Also see a recent Pivotal blog post on migrating legacy code.
2323
Cloud Platforms(formally the artist known as “PaaS”)
24
Static IT infrastructure has become more agile
• Puppet Configuration Management is invented
2005
• Launch of Amazon AWS EC2 Beta
• Google BigTable Paper published
• Facebook becomes publicly available
2006 • Netflix launches Video-on-Demand
• First release of open source Hadoop
2007
• Apple launches the App Store
• Amazon AWS comes out of Beta
2008
25
“Day 2” problems – what ops needs
1. Role-based access to resources
2. Run specified code on demand
3. Coordinate cross service configurations
4. Securely and reliably connect to the public Internet
5. Read and write persistent data
6. Add and remove resources
7. Record internal and external
events
8. Isolate failures to recover from failures
9. Monitor and measure performance and health
10. Detect and determine failure
11. Running a cloud business
12. Resilience to work tomorrow
Source: adapted from “You are Going to Need a Platform, Operational Concerns of the Third Platform,” April 2015.
26
One awesome example of a full cloud platform
More details: http://pivotal.io/platform-as-a-service/pivotal-cloud-foundry; click logos for videos and case studies.
After just 1 year in GA:
• ~$40m in bookings• 40+ customers
