The Software Architecture that is Eating the World Marc Andreessen famously stated that "software is eating the World". In every industry the rules are being rewritten by companies leveraging new software tools and online services to their advantage. This is a massive, game-changing trend that will have transformative effects for decades to come. But how does it work? What makes certain tools and technologies more successful than others? What is the secret weapon of those most productive and disruptive IT organizations? Will this cambrian explosion of tools and services continue exponentially, or will it converge towards a handful of dominant platforms? Join Solomon Hykes, founder and CEO of dotCloud and a pioneer of the PaaS space, and John Rymer, Forrester's Principal Analyst serving Application Development and Delivery Professionals, in an exploration of the architectural blueprint behind the biggest technology shift since the industrial revolution.

1. World of Services
The Software Architecture That is Eating the World
John R. Rymer, Principal Analyst, Forrester
Solomon Hykes, CEO, dotCloud
December 10, 2012

2. Agenda
• Adoption of Cloud Platforms
• 7 Rules of Cloud-Native Development
• Examples
• Conclusion
• Q&A
1

4. The shift begins with the Open Web
NEW TECHNOLOGIES COUPLED WITH NEW THINKING
© 2012 Forrester Research, Inc. Reproduction Prohibited

5. 2010 was the „year of the cloud‟
CLOUD DEVELOPMENT ALMOST DOUBLED THAT YEAR
“In what year did you first build and deploy an application to one of the cloud
platforms you mentioned in the prior question?”
35%
32%
30%
25% 28%
20%
15%
15%
10%
6%
5% 7%
5% 8%
0%
Before 2007 2007 2008 2009 2010 2011 2012
Base: 106 developers with direct experience developing applications using cloud computing environments
Source: Forrester Global Cloud Developer Online Survey, Q3 2012
© 2012 Forrester Research, Inc. Reproduction Prohibited

6. New code in the cloud will grow
A GRADUAL SHIFT TOWARD 50% TO 60% NEW CODE; FEW REPORT 100%
“How much of the code you deploy to the cloud environments of your choice
is new? How do you expect that to change in the future?”
35
30
Today In 2 years
Number of respondents
25 Next year
20
15
10
5
0
0%-20% 20%-39% 40%-59% 60%-79% 80%-99% 100%
New code as percentage of total application
Base: 106 developers with direct experience developing applications using cloud computing environments
Source: Forrester Global Cloud Developer Online Survey, Q3 2012
© 2012 Forrester Research, Inc. Reproduction Prohibited

7. Teams moving to empowerment
November 2010 “Best Practices: Building High-Performance Application Development Teams”

8. 7 RULES OF CLOUD-NATIVE
DEVELOPMENT
Solomon Hykes
7

9. 7 Rules of Cloud-Native
Development
1. Think services, not servers
2. Don’t reinvent the wheel
3. Don’t create silos
4. Don’t get in the way of the developer
5. Cookie-cutter first, customize later
6. Experiment quickly
7. Ship every day
8

10. 1. Think services, not servers
Break down your application
in discrete, reusable components
Libraries that run themselves
Do it from day one
© 2012 Forrester Research, Inc. Reproduction Prohibited
9

12. 3. Don‟t create silos
backend data design security frontend ops
frontend
backend
design ops
performance data
security
11

13. 3 rules of software teams
• Ownership + Focus + Responsibility
– Ownership: 1 team per product
– Focus: 1 product per team
– Responsibility: if you wrote it you fix it
– Don’t form specialized teams. EMBED
specialists into your teams
12

14. 4. Don‟t get in the way of your developers
Functional Requirements Implementation Requirements
• “It has to work for 100,000 • “It has to be Java”
simultaneous connections” • “If you need more
• “We need to go Live by servers, ask Bob for it and
Christmas” wait”
• “It has to pass next • “I heard Node.js is the
quarter’s infosec audit” future, rewrite it all in
• “This can’t go down during Node.js”
next week’s demo. Do • “Your performance will be
whatever it takes” measured by the number of
lines of code written”
© 2012 Forrester Research, Inc. Reproduction Prohibited
13

15. 5. Cookie-cutter first, customize later
Scott VandenPlas, Lead Devops, Obama for America
Requirement: Monitoring at massive scale
“We started with plain old Nagios. Not perfect but
familiar and reliable.”
“Once we hit scale problems, we located the
bottleneck (NRPE) and replaced it with ZERORPC”
“It’s still Nagios, with just enough customization.
Investing that time upfront would have been a
waste of precious time.”
© 2012 Forrester Research, Inc. Reproduction Prohibited
14

16. 6. Experiment quickly
Isaac Wolkerstorfer, CTO, 6Wunderkinder
“1 million users in 9 months. How do we keep
shipping fast without breaking?”
“Service-oriented means we choose the best tool
for each feature.”
“I can use Ruby for one service and PHP for
another. I only refactor when I decide to”
© 2012 Forrester Research, Inc. Reproduction Prohibited
15

17. 7. Ship every day
Start Shipping on Day 1. Don‟t wait for the launch
• Replicate your stack in a sandbox that mirrors the
production environment.
• Deploy to that sandbox every day.
• Give each developer his own sandbox
© 2012 Forrester Research, Inc. Reproduction Prohibited
16

18. We will unmute all attendees to ask questions
QUESTIONS?
17

19. Thank you
John R. Rymer Solomon Hykes
• @forrester • @solomonstre
• @dot_cloud
18