36
Solomon Hykes

World of Services: The Software Architecture that is Eating the World

Embed Size (px)

DESCRIPTION

dotCloud CEO Solomon Hykes explores the seven rules of cloud native development in the World of Services Keynote, Up Cloud Computing Conference 2012 Marc Andreessen discussed the reasons why he thinks software is eating the world, where an online software services takes over the market from a traditional brick and mortar incumbent. Solomon Hykes believes a similar phenomenon is happening in software, in which cloud native development is eating up traditional software architectures. More info: https://www.dotcloud.com/

Citation preview

Page 1: World of Services: The Software Architecture that is Eating the World

Solomon Hykes

Page 2: World of Services: The Software Architecture that is Eating the World

We makedevelopersproductive

Page 3: World of Services: The Software Architecture that is Eating the World

Being a developer in 2013

Page 4: World of Services: The Software Architecture that is Eating the World

Being a developer in 2013

is awesome

Page 5: World of Services: The Software Architecture that is Eating the World

Software is eating the world

Page 6: World of Services: The Software Architecture that is Eating the World

speed=

victory

Page 7: World of Services: The Software Architecture that is Eating the World

Developer productivity

= speed

Page 8: World of Services: The Software Architecture that is Eating the World

HOW?

Page 9: World of Services: The Software Architecture that is Eating the World

7 rulesof cloud-native development

Page 10: World of Services: The Software Architecture that is Eating the World

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

Page 11: World of Services: The Software Architecture that is Eating the World

1.

Think services, not servers

Page 12: World of Services: The Software Architecture that is Eating the World

Your last app

Page 13: World of Services: The Software Architecture that is Eating the World

Your next app

Page 14: World of Services: The Software Architecture that is Eating the World

Services are libraries that run themselves

Page 15: World of Services: The Software Architecture that is Eating the World

2.

Don’t reinvent the wheel

Page 16: World of Services: The Software Architecture that is Eating the World
Page 17: World of Services: The Software Architecture that is Eating the World

What differentiates you?

Page 18: World of Services: The Software Architecture that is Eating the World

Focus

Page 19: World of Services: The Software Architecture that is Eating the World

Focus

Outsource the rest

Page 20: World of Services: The Software Architecture that is Eating the World

Justin KanCEO, Exec

“Without these ready-to-use cloud services we never could have launched so fast with a team so small”

Page 21: World of Services: The Software Architecture that is Eating the World

3.

Don’t create silos

Page 22: World of Services: The Software Architecture that is Eating the World

Web DBA Ops Systems

Page 23: World of Services: The Software Architecture that is Eating the World

Web DBA Ops Systems

Page 24: World of Services: The Software Architecture that is Eating the World

Product A

Product B

Product C

Page 25: World of Services: The Software Architecture that is Eating the World

One team per product

One product per team

Run what you write

Page 26: World of Services: The Software Architecture that is Eating the World

4.

Don’t get in the way

of the developer

Page 27: World of Services: The Software Architecture that is Eating the World

Functionalrequirements

Technicalrequirements

“It has to work for 100,000 simultaneous

connections”

“We need to go Live by Christmas”

“It has to pass next quarter’s infosec audit”

“This can’t go down during next week’s

demo. Do whatever it takes”

“It has to be Java”

“If you need more servers, ask Bob for it

and wait”

“I heard Node.js is the future, rewrite it all in

Node.js”

“Your performance will be measured by the

number of lines of code written”

Page 28: World of Services: The Software Architecture that is Eating the World

5.

Cookie-cutter first,

customize later

Page 29: World of Services: The Software Architecture that is Eating the World

Scott VandenplasLead devops, Obama for America

“We started monitoring 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 awaste of precious time.”

Page 30: World of Services: The Software Architecture that is Eating the World

6.

Experiment quickly

Page 31: World of Services: The Software Architecture that is Eating the World

Isaac WolkerstorferCTO, 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”

Page 32: World of Services: The Software Architecture that is Eating the World

7.

Ship every day

Page 33: World of Services: The Software Architecture that is Eating the World

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

Page 34: World of Services: The Software Architecture that is Eating the World

It’s all about

speed

Page 35: World of Services: The Software Architecture that is Eating the World

It’s all aboutdeveloper productivity

Page 36: World of Services: The Software Architecture that is Eating the World

Thank you!