Cloud Native Apps…
from a user point of view
Alexis Richardson
CEO, Weaveworks
WSO2 keynote – June 2nd 2015
About me
• Metalogic
• Cohesive Networks (fka CohesiveFT)
• RabbitMQ
• VMware / Pivotal – vFabric, Spring, Redis,
Cloud Foundry (and even OpenStack..) et al.
• Weaveworks
Why start another company?
2015
Like 1995 but 1000x more awesome(*)
(*) if you want to make customers happy using software
2015
Like 1995 but 1000x more awesome(*)
(*) if you want to make customers happy using software
All Hail Mary Meeker
http://www.kpcb.com/internet-trends
Global
Top 5 public eCommerce companies
approx same $volume as Swiss GDP
Mobile
On Demand
What matters?
xxx
Our North Star is to win more of our
members’ “moments of truth”
Our North Star is to win more of our members’ “moments of truth”.
Those decision moments are, say, on Thursday 7:15 pm or Monday 2:40 am when our
member wants to relax, enjoy a shared experience with friends and family, or is just
bored. They could play a video game, surf the web, read a magazine, channel surf
their MVPD/DVR system, buy a pay-per-view movie, put on a DVD, turn on Hulu or
Amazon Prime, or they could tap on Netflix. We want our members to choose Netflix
in these moments of truth.
We win those moments of truth when members expect, based on their prior
experience with us, that Netflix will be pleasurable, compared to all those other
options. The pleasure comes from our simple experience for choosing, control over
when to start/pause/resume the video, and from content that suits their taste and
their mood.
When we deliver enjoyment, members watch more Netflix, continue their
membership, and evangelize Netflix to their friends.
2015 – Netflix has 60M+ subscribers, adding >4M per quarter
Implications for everyone else?
Key takeaways so far
• On demand services, powered by
software, are the new MUST HAVE
• And they are core to your business –
cannot be outsourced
• Businesses: ally with developers or die
The Technology
What developers need to know
2015 “must have” requirements
•Self Service
•Agile & Always On
•Flexible Deployment
Implications of Self Service
• 1-click install & uninstall
• Pay per use, never pay to set up & provision
• Global scale & customer base
• Measure everything
• Test & adapt & upgrade in real time
 PROFIT!
For Developers – customer “me want it NOW”
Best way of think about this? App Store
Agile +
Always On

DevOps
DevOps Example
• Target, talk at DevOps enterprise summit, 2014
• Release frequency UP 100x
– 1/quarter  100/quarter
• Release size DOWN - 100x
• Errors and production issues DOWN by 90%
• Costs DOWN by 50%
For developers:
• Same team, much less waste, better products, happier
customers, continuous delivery..
xxx
Business value – better to spend
$100M on making House of Cards,
than on building a data center
Flexible Deployment
• Cloud
• Global infra for metered on demand services
• Super scalable, Ideal for DevOps, “Always On”, CI
Implication for developers
• Basically a RANDOM environment
• Can your app pass the 20% test?
• Can your app monitor & measure everything?
Key Takeaways so far!
• Developers:
– Optimize for speed instead of cost
– Assume that cloud is random
• This applies to:
– What you design
– How you develop
– Where you deploy
In the Moment of Truth, the customer doesn’t care about you,
they care about “me”
Not just Netflix, also:
GOOGLE
Google Scale for all?
• 2 billion containers started per week
• 100 billion per year
• Google has ~1% of world’s servers
Current potential of 100*100B = 10 trillion
server side containers per year globally
But there are 10-50M developers
Automation
Choice
Composable
Developing in the ‘me’ generation
• Google shows we need automation to scale
• Developers tell us they need choice
• Reject “one size fits all”. Embrace “composable”
 Cloud Native
Cloud Native Apps
Container packaged
Dynamically Scheduled
Micro-services oriented
Cloud Native Apps
In a nutshell: everything is decoupled for scale
Decouple software from physical deployment
Decouple users from service instances
Decouple software into components
Containers!
Fast, Easy, Portable Packaging
• Lightweight VMs – mobile & isolated env.
• Enables portability & idempotency
• More efficient than VMs – “lean and fast”
• Docker adds “make it easy for developers”
What is Docker?
Docker at the Moment of Truth
• Jason Hoffman:
– I think Linux took off because of package
management. I think that’s basically it. Docker’s
taking off because it’s the new package
management. It’s just that simple.
Convenience
Safety?
Managing Docker in enterprise
• Performance Management
• Security
• Monitoring
• Provenance
• Policy
 It’s in the (weave) works
Dynamically Scheduled & Metered
• Mesosphere
• Kubernetes & GKE
• Docker Swarm
• Cloud Foundry Diego / LatticeCF
• Amazon ECS
• Azure?
 WSO2 Stratos uses Kubernetes, so does Fabric8,
so does OpenShift…
Microservices
All Hail Adrian Cockroft
http://www.slideshare.net/adriancockcroft/d
ockercon-state-of-the-art-in-microservices
Wix
Summary
• User needs have changed
• Business needs lots more developers
• Cloud Native is the way forward
Adapt or …
So why I am doing Weave?
Plumbing for cloud native applications
• Simple, Portable, Transparent
• Cloud Native apps made easy for developers
• NO need to rewrite app code or re-tool apps!
Check out http://weave.works
Cloud Native Apps ... from a user point of view

Cloud Native Apps ... from a user point of view

  • 1.
    Cloud Native Apps… froma user point of view Alexis Richardson CEO, Weaveworks WSO2 keynote – June 2nd 2015
  • 2.
    About me • Metalogic •Cohesive Networks (fka CohesiveFT) • RabbitMQ • VMware / Pivotal – vFabric, Spring, Redis, Cloud Foundry (and even OpenStack..) et al. • Weaveworks
  • 3.
  • 5.
    2015 Like 1995 but1000x more awesome(*) (*) if you want to make customers happy using software
  • 6.
    2015 Like 1995 but1000x more awesome(*) (*) if you want to make customers happy using software
  • 7.
    All Hail MaryMeeker http://www.kpcb.com/internet-trends
  • 8.
  • 10.
    Top 5 publiceCommerce companies approx same $volume as Swiss GDP
  • 11.
  • 14.
  • 17.
  • 20.
    xxx Our North Staris to win more of our members’ “moments of truth”
  • 21.
    Our North Staris to win more of our members’ “moments of truth”. Those decision moments are, say, on Thursday 7:15 pm or Monday 2:40 am when our member wants to relax, enjoy a shared experience with friends and family, or is just bored. They could play a video game, surf the web, read a magazine, channel surf their MVPD/DVR system, buy a pay-per-view movie, put on a DVD, turn on Hulu or Amazon Prime, or they could tap on Netflix. We want our members to choose Netflix in these moments of truth. We win those moments of truth when members expect, based on their prior experience with us, that Netflix will be pleasurable, compared to all those other options. The pleasure comes from our simple experience for choosing, control over when to start/pause/resume the video, and from content that suits their taste and their mood. When we deliver enjoyment, members watch more Netflix, continue their membership, and evangelize Netflix to their friends.
  • 23.
    2015 – Netflixhas 60M+ subscribers, adding >4M per quarter
  • 24.
  • 28.
    Key takeaways sofar • On demand services, powered by software, are the new MUST HAVE • And they are core to your business – cannot be outsourced • Businesses: ally with developers or die
  • 30.
  • 31.
    2015 “must have”requirements •Self Service •Agile & Always On •Flexible Deployment
  • 32.
    Implications of SelfService • 1-click install & uninstall • Pay per use, never pay to set up & provision • Global scale & customer base • Measure everything • Test & adapt & upgrade in real time  PROFIT! For Developers – customer “me want it NOW”
  • 33.
    Best way ofthink about this? App Store
  • 34.
  • 35.
    DevOps Example • Target,talk at DevOps enterprise summit, 2014 • Release frequency UP 100x – 1/quarter  100/quarter • Release size DOWN - 100x • Errors and production issues DOWN by 90% • Costs DOWN by 50% For developers: • Same team, much less waste, better products, happier customers, continuous delivery..
  • 37.
    xxx Business value –better to spend $100M on making House of Cards, than on building a data center
  • 38.
    Flexible Deployment • Cloud •Global infra for metered on demand services • Super scalable, Ideal for DevOps, “Always On”, CI Implication for developers • Basically a RANDOM environment • Can your app pass the 20% test? • Can your app monitor & measure everything?
  • 41.
    Key Takeaways sofar! • Developers: – Optimize for speed instead of cost – Assume that cloud is random • This applies to: – What you design – How you develop – Where you deploy In the Moment of Truth, the customer doesn’t care about you, they care about “me”
  • 43.
    Not just Netflix,also: GOOGLE
  • 44.
    Google Scale forall? • 2 billion containers started per week • 100 billion per year • Google has ~1% of world’s servers Current potential of 100*100B = 10 trillion server side containers per year globally But there are 10-50M developers
  • 45.
  • 46.
  • 47.
  • 48.
    Developing in the‘me’ generation • Google shows we need automation to scale • Developers tell us they need choice • Reject “one size fits all”. Embrace “composable”  Cloud Native
  • 49.
    Cloud Native Apps Containerpackaged Dynamically Scheduled Micro-services oriented
  • 50.
    Cloud Native Apps Ina nutshell: everything is decoupled for scale Decouple software from physical deployment Decouple users from service instances Decouple software into components
  • 51.
    Containers! Fast, Easy, PortablePackaging • Lightweight VMs – mobile & isolated env. • Enables portability & idempotency • More efficient than VMs – “lean and fast” • Docker adds “make it easy for developers”
  • 52.
  • 53.
    Docker at theMoment of Truth • Jason Hoffman: – I think Linux took off because of package management. I think that’s basically it. Docker’s taking off because it’s the new package management. It’s just that simple.
  • 54.
  • 55.
  • 56.
    Managing Docker inenterprise • Performance Management • Security • Monitoring • Provenance • Policy  It’s in the (weave) works
  • 57.
    Dynamically Scheduled &Metered • Mesosphere • Kubernetes & GKE • Docker Swarm • Cloud Foundry Diego / LatticeCF • Amazon ECS • Azure?  WSO2 Stratos uses Kubernetes, so does Fabric8, so does OpenShift…
  • 58.
  • 59.
    All Hail AdrianCockroft http://www.slideshare.net/adriancockcroft/d ockercon-state-of-the-art-in-microservices
  • 63.
  • 66.
    Summary • User needshave changed • Business needs lots more developers • Cloud Native is the way forward
  • 67.
  • 68.
    So why Iam doing Weave? Plumbing for cloud native applications • Simple, Portable, Transparent • Cloud Native apps made easy for developers • NO need to rewrite app code or re-tool apps! Check out http://weave.works

Editor's Notes

  • #22 http://files.shareholder.com/downloads/NFLX/2441659654x0x656145/e4410bd8-e5d4-4d31-ad79-84c36c49f77c/IROverviewHomePageLetter_4.24.13_pdf.pdf Netflix Long Term View
  • #36 http://www.activestate.com/blog/2015/04/microservices-revisited-interview-adrian-cockcroft
  • #37 http://java.dzone.com/articles/cloud-native-application
  • #39 https://medium.com/s-c-a-l-e/talking-microservices-with-the-man-who-made-netflix-s-cloud-famous-1032689afed3
  • #40 Massimo blog post: http://it20.info/2014/12/cloud-native-applications-for-dummies/ A good litmus test to see if you are running a legacy application or a cloud native application is as follows. Invite me to your data center at 11AM on a Monday morning to turn off and destroy 20% of the instances you have in production. If your application deployment self-fixes itself without any work on your part and if there was minimal to no disruption in your end-user experience then you are running a proper cloud native application. If, on the other hand, you go like “Oh my god what did you do? I have a week of work in front of me now!” all while your phone is ringing like crazy then welcome to the real world along with the remaining 95% of the people.
  • #41 http://www.theregister.co.uk/2013/03/18/servers_pets_or_cattle_cern/
  • #67 http://stackshare.io/wix/scaling-wix-to-60m-users---from-monolith-to-microservices