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

Post on 31-May-2015

1.142 views 0 download

Tags:

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/

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

Solomon Hykes

We makedevelopersproductive

Being a developer in 2013

Being a developer in 2013

is awesome

Software is eating the world

speed=

victory

Developer productivity

= speed

HOW?

7 rulesof 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

1.

Think services, not servers

Your last app

Your next app

Services are libraries that run themselves

2.

Don’t reinvent the wheel

What differentiates you?

Focus

Focus

Outsource the rest

Justin KanCEO, Exec

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

3.

Don’t create silos

Web DBA Ops Systems

Web DBA Ops Systems

Product A

Product B

Product C

One team per product

One product per team

Run what you write

4.

Don’t get in the way

of the developer

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”

5.

Cookie-cutter first,

customize later

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.”

6.

Experiment quickly

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”

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

It’s all about

speed

It’s all aboutdeveloper productivity

Thank you!