Successfully reported this slideshow.
Your SlideShare is downloading. ×

The Cloud Native Journey

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Loading in …3
×

Check these out next

1 of 35 Ad

The Cloud Native Journey

Download to read offline

The ability to deliver software is no longer a differentiator. In fact, it is a basic requirement for survival. Companies that embrace cloud native patterns of software delivery will survive; companies that don’t - will not.

In this webinar, we will:

- Look at the common patterns that distinguish cloud native companies and the architectures that they employ.

- Discover that an opinionated platform, one that stretches from the infrastructure all the way to the application framework, rather than ad-hoc automation, is an essential component to an enterprise's cloud native journey.

- Show that the combination of Pivotal Cloud Foundry and Spring is the complete cloud native platform.

Speaker:
Faiz Parkar
DIRECTOR OF PRODUCT MARKETING
As Director of Product Marketing for Pivotal in the Europe, Middle East and Africa region, Faiz Parkar loves working at the intersection of cloud native platforms, big data/analytics and agile application development to help organisations deliver compelling data-driven software experiences for their customers. With more than 25 years experience in the IT industry, Faiz has helped organisations large and small to take advantage of technology transitions from proprietary systems to client/server, from physical infrastructure to virtual, and from virtual infrastructure to cloud. His mission now is to help organisations accelerate their digital transformation journey and reinvent themselves as the digital leaders of the future.

The ability to deliver software is no longer a differentiator. In fact, it is a basic requirement for survival. Companies that embrace cloud native patterns of software delivery will survive; companies that don’t - will not.

In this webinar, we will:

- Look at the common patterns that distinguish cloud native companies and the architectures that they employ.

- Discover that an opinionated platform, one that stretches from the infrastructure all the way to the application framework, rather than ad-hoc automation, is an essential component to an enterprise's cloud native journey.

- Show that the combination of Pivotal Cloud Foundry and Spring is the complete cloud native platform.

Speaker:
Faiz Parkar
DIRECTOR OF PRODUCT MARKETING
As Director of Product Marketing for Pivotal in the Europe, Middle East and Africa region, Faiz Parkar loves working at the intersection of cloud native platforms, big data/analytics and agile application development to help organisations deliver compelling data-driven software experiences for their customers. With more than 25 years experience in the IT industry, Faiz has helped organisations large and small to take advantage of technology transitions from proprietary systems to client/server, from physical infrastructure to virtual, and from virtual infrastructure to cloud. His mission now is to help organisations accelerate their digital transformation journey and reinvent themselves as the digital leaders of the future.

Advertisement
Advertisement

More Related Content

Slideshows for you (20)

Viewers also liked (20)

Advertisement

Similar to The Cloud Native Journey (20)

More from VMware Tanzu (20)

Advertisement

Recently uploaded (20)

The Cloud Native Journey

  1. 1. Cloud Native Journey Faiz Parkar Director, Product Marketing Pivotal EMEA @_CloudNinja
  2. 2. DIGITAL DISRUPTION IS CHANGING THE WAY BUSINESS IS DONE
  3. 3. EXPERIENCES ARE BEING REIMAGINED See a Doctor in minutes at a time and location that suits you Get offers for stuff you like when you’re where you can buy Get meals from the best local restaurants in under 10 minutes
  4. 4. must be built, they can’t be bought. Superior digital experiences
  5. 5. 75% of application development supporting digital business will be built not bought by 2020 Source: Gartner
  6. 6. In a world of digital interactions, organizations will deliver business innovation through software: Every business will be a software business
  7. 7. Software is your core differentiator  In-sourcing software development  Shift from off the shelf to custom purpose-built  Building internal expertise in modern software development approaches “In the past 90% of car value was in hardware, we expect 50% of value will be in hardware and the other 50% divided by software and experiences” Don Butler Executive Director, Connected Vehicles
  8. 8. HOW TO BECOME A “SOFTWARE COMPANY”? Innovate Automate Record Mainframe / PC / Web IT Mode 1 Safety, Accuracy 1960 IT Mode 2 Exploratory, Rapid, Non-linear Record, Automate, Learn Cloud-Native Cloud / Mobile / IoT Innovate Iterate 2000 2016 “BIMODAL IT” (GARTNER)
  9. 9. So what do the Cloud Natives do? $6B $50B $41B $25B $33.5B
  10. 10. SPEED UBIQUITY* SCALE SAFETY (MOBILE)
  11. 11. Continuous Delivery
  12. 12. Delivery Continuous
  13. 13. Day One Day Two and Beyond Deliver Continuously
  14. 14. Continuously Delivered Microservices Loosely coupled service oriented architecture with bounded contexts If every service has to be updated in concert, it’s not loosely coupled! If you have to know about surrounding services you don’t have a bounded context.
  15. 15. Cloud native and microservice models are moving into the Fortune 500 “Two people built an app and got it into the App Store in five weeks” “I said to my vendors, I don’t want five years ago. I want five years from now. “The adopters we speak to today, like GE, HP, Equinix, PayPal, Capital One, Goldman Sachs, Airbnb, Medallia, Square, and Xoom say that microservices are well worth the tradeoffs.”
  16. 16. Cloud Native • Microservices architecture • API-first design • Fault-tolerant and resilient design • Cloud-agnostic runtime implementation • Bundled metrics and monitoring • Proactive failure testing Cloud Resilient Cloud Friendly Cloud Ready • No permanent disk access • Self-contained application • Platform-managed ports and networking • Consumes platform-managed backing services • 12 Factor App methodology • Horizontally scalable • Leverages platform for high availability Cloud Native Maturity Model
  17. 17. Azure VMware vSphere Seneca Application Frameworks Container Schedulers Automation Tools Cloud Technology Bingo Spring Boot Seneca Ruby on Rails Dropwizard Mesos ChronosDocker Kubernetes SALT Chef Puppet Ansible Cloud adoption with non-cloud native applications, unopinionated tools and adhoc automation Amazon Web Services OpenStack Cloud Infrastructure
  18. 18. the ratio of app developers to platform developers at “web scale” companies
  19. 19. UNDIFFERENTIATED HEAVY LIFTING
  20. 20. Application Framework Infrastructure Automation Platform Runtime Language framework for microservice-based architectures including components for service discovery, metrics and circuit breakers. Application container runtime with attachable backing services, automated CI/CD, routing, health management and logging. A single deployment API for provisioning for bit-for-bit, consistent, self- healing deployments across any private or public cloud. Dev Dev Ops Ops Spring Cloud Spring Boot BOSH Cloud Foundry Pivotal Cloud Foundry Pivotal Contract: 12 Factor Application Contract: BOSH Release
  21. 21. SPRING BOOT OMAKASE TWELVE FACTOR APPS http://start.spring.io
  22. 22. SPRING CLOUD http://cloud.spring.io https://network.pivotal.io/products/p-spring-cloud-services OMAKASE DISTRIBUTED SYSTEMS
  23. 23. SPRING CLOUD DATA FLOW OMAKASE BATCH AND STREAM DATA PROCESSING http://cloud.spring.io/spring-cloud-dataflow
  24. 24. 24 IAAS PAAS Cloud Platform Evolution BEFORE Virtualization Platform Operating System Database Web Server Messaging Your Application Code Physical Servers App AFTE R Infrastructure concerns Technology silos Matrix of specialization Business focus All about the applications Line-of-sight to customers App App
  25. 25. Cloud Foundry: The Industry’s Open Cloud Standard Gold Silver Platinum T E A M
  26. 26. Container Scheduling Application Framework ServicesPlatform Runtime Routing DatabaseConfigurationService Discovery Big Data Object Storage Mobile Build CI User ProvidedLogging & Metrics Messaging Circuit Breakers12 Factor Apps RESTful Services Microservices .NETSpring Boot Node.jsRuby on Rails Operations Zero Downtime Deployments Failover & Recovery Scaling Security Patching Platform Upgrades Infrastructure OpenStack AmazonVMware
  27. 27. 27 Cloud Native DevOps Continuous Delivery ContainersMicro services
  28. 28. Flexibility without getting locked in “It’s definitely around speed to market, but it’s also about getting it right faster” “Should the bank elect to use public cloud services… we don’t have to touch the apps to do it” “Bank provisioned 2 transaction processing apps onto Cloud Foundry in half a day” George Sherman CIO Global Technology Infrastructure
  29. 29. Faster Time to Market People have taken notice of the rapid rate in which we’re able to deliver applications. With Cloud Foundry we’ve transitioned to a situation where those same people who were moving files before may be managing Cloud Foundry Ops manager in a role of being a partner instead of being a barrier. MyHealth By Humana Delivered: 2.5 months Cue by Humana Delivered: 5 weeks “ ”
  30. 30. “Think of a product on a Monday and deliver on Friday.”
  31. 31. - Richard Leurig, SVP Innovation Development Center “Moving to a Cloud Native Platform is more than a technological transformation. It’s a new way to develop products… It’s the most exciting thing we’ve done in the last 12 months.”
  32. 32. “Now with Cloud Foundry and Pivotal, operations that used to take weeks can take minutes or less.” - Francois Andry, Sr. Director of Architecture, HealthSuite Digital Platform
  33. 33. Cloud Native Platform to Transform your Enterprise BUSINESS • Align IT with business goals • Respond to changes in marketplace quickly • Capture new business opportunities DEVELOPMENT • Self-service with automated provisioning • Rapidly iterate, deploy to production faster • Framework with integrated tools OPERATIONS • Operational agility • Deploy consistent platforms with application visibility • High availability with instant scaling
  34. 34. How to get started on your Cloud Native journey http://bit.ly/cloud-native-book http://pivotal.io/cloud-foundry-the-cloud-native-platform
  35. 35. Let’s build something MEANINGFUL

Editor's Notes

  • You might think that such digital innovation is all coming out of Silicon Valley and therefore only disrupting companies in the US. But as the internet is global, a digital startup on the other side of the world can well compete against traditional companies in other countries. We are also seeing huge investments in digital startup companies based on this side of the pond.
    Starbucks, a global brand makes use of big data analytics to target customers near their coffee shops with compelling personalised offers
    Uber already in 68 cities in EMEA and 19 out of 28 EU countries – despite protests in some countries, they will be present in 24-25 member states by the summer of 2016. Not content with transforming the transportation industry they are now going after adjacent markets: most recently introducing a food delivery service in Barcelona! Source: http://www.euractiv.com/sections/innovation-industry/uber-chief-uber-and-europe-definitely-conversation-worth-having-313851
    Babylon – based in UK gives you the ability to chat and video conference with a Doctor at a time and location that suits you – no need to go through the hassle of waiting for hours or days for a Doctor’s appointment! http://babylonhealth.com


  • Want to deliver a superior digital experience for your customers?

    It must be built, it can’t be bought.
  • It's about building software. The new paradigm is, “you are either a builder or a buyer.”
  • Enterprise starting to view software as a core differentiator
    Insourcing software development
    http://mobile.blogs.wsj.com/cio/2014/05/22/the-morning-download-delta-latest-company-to-bring-more-software-in-house/
    Shifting from commercial off-the-shelf apps to custom purpose-built
    Take-away:
    Enterprise needs to rapidly deliver and iterate on mobile apps, with internal teams leveraging state-of-the-art methods, tools and platforms

  • “Bimodal IT is the practice of managing two separate, coherent modes of IT delivery, one focused on stability and the other on agility. Mode 1 is traditional and sequential, emphasizing safety and accuracy. Mode 2 is exploratory and nonlinear, emphasizing agility and speed.”
  • So, if that’s true, what is it that the cloud natives do?
  • Well, in my quest to understand these companies and how they operate, I’ve identified four key patterns. Speed, safety, scale, and what I’m now calling “ubiquity.” I used to call this mobile, but what I’m really trying to highlight is the idea that anybody, anywhere, can at anytime interact with your services (not just mobile – could be smartphone, could be watch, could be other wearable devices).
    Speed is obvious - we can innovate, experiment, deliver value quickly.
    Safety balances speed with the simultaneous ability to maintain stability, availability, and durability.
    And scale refers to our ability to elastically respond to changes in demand.

  • The cloud natives practice continuous delivery. Well what does that mean? It may help to invert the phrase.
  • Delivery Continuous. Or perhaps better, if we fix the grammar…
  • Deliver Continuously. You see, it’s not enough to deploy something. That’s just Day One. You also have to deploy again, and again, and again. And when you do that, you can’t break stuff. That’s day two, day 3, day 4 …and beyond.
  • So what are we continuously delivering? MICROSERVICES.

    What are microservices? Well here’s Adrian Cockcroft’s, chief architect from netflix definition.

    SOA. (SOA not bad, just how it has been implemented in the past)

    Loosely coupled - I can deploy my service any time I want. I can deploy new versions of my microservice at any time without having to refer to other teams/microservices. Need to maintain contract for interfacing.

    One of the ways you can do that is through Bounded context – services that don’t know anything about surrounding services other than their API’s - not their internal implementations. Bounded contexts protect internal implementations.
  • We’re seeing companies like like Lockheed Martin, BMW and Philips that are incubating cloud-native design in their organizations. These companies are shipping apps to production.



    Source: WSJ http://blogs.wsj.com/cio/2015/10/05/innovate-or-die-the-rise-of-microservices/
    Antonio Melo, Humana, CF Summit 2015
  • These architectures are something you can incubate at your organization. One of our customers in the finance space, JPMC, has developed a cloud-native maturity model that helps to categorize the movement from monolith to microservices. You have a path both for greenfield apps, and migration or modernization of existing applications to make them cloud-ready.

  • How are many enterprise moving to an cloud native application designs? Technology bingo with different tools. A cloud and automation tools a-la-carte today, using a combination of individual cloud services or technologies: Just EC2 + services. Just Docker. Docker with Puppet/Chef/Ansible/SALT. MesosSphere or Kubernetes with Docker on EC2. etc etc.

    Ad hoc tools are particularly difficult to update, the “Day 2” operation side. When you invest by combining all range of open source projects together,, you end up spending a huge amount of time working on integration. If you’ve got a dozen different open source projects in production, you’ll have to curate thousands of pull requests a wee,, into a secure package. This is an ongoing effort



  • What’s cool about Pivotal is the our breadth of real world experience. You get to talk to people all of the time that built amazing things. And so I asked folks like Ben Black, who was part of the birth of AWS, and Adrian Cole, who spent time at Netflix, Square, and Twitter — “what’s the ratio of developers working on real business facing apps vs. platform?” Across the board, the answers are within some small delta of 10:1.

    The real question becomes - where do you want your best engineers spending their time? Solving the problems of delivery? Or delivering great software?
  • Ultimately, the degree to which you expend human capital on building delivery mechanisms is a prime indicator of your likelihood of failure.

    So we’re going to spend the rest of our time talking about an opinionated platform, which in my mind is the only way you can achieve this level of effectiveness, because it destroys the need <TRANSITION> to perform such undifferentiated heavy lifting and simultaneously provides you with the capabilities you need to continuously deliver digital experiences at scale and speed. Don't waste time figuring out structure for your platform - use all of your brain power on differentiation.

    Because that’s what your competition will be doing.
  • An opinionated set of frameworks and tools for delivering distributed applications.

    We have been working ‘Cloud native application platform in a box’. PCF is the 1st and only cloud native vendor available today.

    The differentiator are these contracts between your application and the runtime, and between the runtime and the infrastructure.

    12 Factor application design lets us built applications that are suitable for CI/CD.

  • I’m going to start at the top of the Pivotal stack and work my way through all of it’s different interesting layers, starting with Spring Boot.

    Spring has been around for a long time. The amount of boiler plate work in dependency management and initial configuration of a Spring app used to be a lot of work, made it hard to get started. One of the things that’s happened in the last 3 years is that we’ve taken the best practices of dependency management and boilerplate configuration and baked those strong opinions into the framework.

    So now if you go to start.spring.io, you plug in your Maven co-ordinates, you tell it your version of Java, what build system (Maven or Gradle), which version of Spring Boot you want to run with, check off a set of boxes indicating which components you want, click a button and you get a zip file containing the dependency management and boilerplate configuration pushed down into the bits of the framework. So what you get is an application that’s immediately run-able, that you can start writing code in immediately that will actually make you money.

    Allows you to build applications which are very consistent with the principles of 12-factor applications, which we’ll talk about later.
  • So Boot allows you to build individual microservices very easily, but how do you take those individual microservices and compose them?

    When you build distributed systems, you run into additional challenges. Configuration management, service discovery, client side routing and load balancing, fault tolerance, monitoring.

    As it turns out, one of the best known ways to solve these challenges is using the Netflix open source tools like Zuul, Ribbon, Hystrix, and Eureka. The delta between you cloning Netflix’s github repository and actually having a production ready service that you’re comfortable with operating is actually quite large.

    So Spring has done what it’s always done: take the complexity and simplify it for the enterprise developer who doesn’t have time to fight that complexity. Using the familiar Spring programming model, using same auto configuration techniques ground in Spring Boot, we’ve taken these Netflix OSS tools and baked them into Spring Cloud.
  • Some application workloads have special requirements. How do I do message-driven microservices? How do I configure batch jobs? How do I do stream data processing? These are just special cases of what Spring Boot and Spring Cloud do well. Sping Cloud Data Flow takes those components and builds on top of that further opinionated foundations for wiring together individual microservices that are processing streams of messages, and taking those components and creating streams or batch flows, or just loosely coupled message driven structures. But at the same time, all of those applications are still just Spring Boot and Spring Cloud applications so we don’t lose any of the loose coupling and ease of deployment, but we get these additional benefits on top of that.
  • Traditionally, developers have to know how plumbing and wiring works in order to deliver working software. That leads to bloat and missed deadlines.
    Middleware teams are siloed and integration is challenging
    Infrastructure teams have specialists who are either overloaded or waiting for work. It’s inefficient.

    The winners in the era of cloud organize their teams around business capabilities and APIs
    The application teams worry about business logic, not plumbing.
    The platform team is concerned with providing the self-service capabilities the app devs need
    The infrastructure teams can see the end users. They aren’t in the dark and they are programmable.
  • Not only did we start from day one on an open-source basis, but we went out of our way to recruit others in the industry to join with us in a Foundation. Our partners in the governance of that foundation include IBM, HP, SAP, Intel, and about 40 other companies. The biggest technology companies in the world are rallying behind Cloud Foundry to make it the open cloud standard for the industry and allow enterprises of any size and scale to build modern cloud applications, whether that really starts in their data center or they start using hybrid or public cloud infrastructures.



  • And then there is the platform runtime itself, which brings its own strong opinions from the infrastructure layer up, including how best to orchestrate IaaS clouds to deploy, update, and manage the health of the platform itself, all the way up to elastically managing the lifecycle of your applications and their backing services. Along the way, we’ve created a hand-in-glove relationship between the Spring App Framework Platform and the Pivotal CF Elastic Runtime Platform.


    Let’s go into a little more detail about the components that actually make up Pivotal Cloud Foundry.
    We the applications, which is where this starts. You need to select an application framework that lets you build these distributed systems.
    We have a platform runtime, which handles routing etc. Attachable backing services for data, CI, and whatever your need
    This is built on an operations layer
    It does all this on Vmware and Openstack in your data center, plus Amazon public cloud. If each of those infrastructures was an electricity grid, Cloud Foundry would be the travel adapter. You get a single deployment API and set of backing services, so you can port applications with no code changes.
    It comes down to this: Would you rather have developers spend their time building a platform, or using one?


    Dev and Ops teams have to change together
    Our customer base was struggling with partial transitions and continuous delivery



  • At Pivotal, we really see these trends as manifestations and facets of the same thing – that we call CLOUD NATIVE.

    CLOUD NATIVE is the coming together of tools, frameworks and building modern software on a cloud infrastructure
  • Source: WSJ
  • Other quotes:
    The most impressive things to me about Cloud Foundry are the ability to scale with cf scale, to be able to immediately response to customer demand, also the ability to recover from failure.

    Pivotal Cloud Foundry has impacted the Operations team in unexpected ways. They don’t really have to do much in terms of maintenance. Its just works.
  • Andy Zitney, All State.
    The first few minutes of the speech are the best: “We have to transform because Google is licensed to sell insurance in 40 states”
    What if Google got into your industry? It’s not their capital that makes them a threat. It’s their ability to win with software.

    "The most dangerous phrase is: We've always done it this way ... That's no longer a valid reason not to change because everyone is going to disrupt the insurance industry… This industry is going to see an Uber-like disruption at a speed and pace that we can't react. So we go out and find a platform to help us deliver something that in the past we never could have” 

    "No longer wait for 6 months to launch a new product ... conceive a product on a Monday, launch it on a Friday” 

    "Cloud Foundry is a great platform for a technologist, but even better for someone who wants to change an industry or how a company thinks” 

    "Moving from 100 days to minutes is what Cloud Foundry gives us"
  • And it’s getting results. One of our customers is Corelogic, a 3 billion dollar company in the finance and property space. The senior vice president for innovation spoke at our annual Summit conference this year, and told the crowd that this platform is the most exciting project that Corelogic has done in the last 12 months.
  • At Philips, they’re using the platform for applications in the healthcare space, such as analysis of MRI scans and other medical diagnostics. The senior director ofarchitecture for their healthsuite digital platform was able to use Pivotal Cloud Foundry to bring operations that used to take weeks, down to minutes.
  • So what does an open cloud platform provide for your enterprise?

    For Businesses, an open cloud platform allows IT to keep up with the accelerated pace of change required to compete today, and allows business leaders to nimbly respond to new opportunities.

    For Developers, the attributes of an open cloud platform support Faster Time To Market for new applications. They have access to integrated tools such as mobile + data services. They can leverage open source technologies for standards that ensure better interoperability. All of this is in support agile and iterative practices that lead to a faster time to production deployment.

    For Operations, the open cloud platform is about Continuous Delivery, with No Downtime, availability levels that meet the most stringent large enterprise requirements, and Instant scaling at the push of a button. These attributes are designed to ensure consistency, delivered via time saving automation.



  • From Silicon Valley…

×