Aw (3) webinar serverless-fisher-rymer

Aw (3) webinar serverless-fisher-rymer

• 1.
  © Copyright 2017Pivotal Software, Inc. All rights Reserved. Version 1.0 November 2018 Host: Richard Seroter, Pivotal Guests: Mark Fisher, Pivotal, John Rymer, Forrester Everything you wanted to know about serverless, but were afraid to ask!
• 2.
  What we’ll cover today Definitions,mapping to what you’re doing now, useful next steps • Review research about current IT trends • Defining serverless and functions-as-a-service • Today’s landscape • How serverless maps to existing priorities • Workload for serverless platforms • Where Knative, project riff and Pivotal Function Service (PFS) come in • Getting started
• 3.
  3© 2018 FORRESTER.REPRODUCTION PROHIBITED. New tech & processes emerging, evolving Base: 3,228 global developers. Source: Forrester Analytics’ Business Technographics Developer Survey, 2018 24% 24% 26% 28% 29% 31% 33% 33% 36% 36% 39% 40% 41% Value stream management Serverless architecture Low-code development tools? (not really a process, but maybe ask about rapid development?) Loosely coupled architecture Cloud resident CI tools Microservices Containers Cloud resident development environment Continuous delivery Design thinking Functional programming DevOps Automated testing Agile software development Which of the following processes or technologies does your company currently use? 56%
• 4.
  4© 2018 FORRESTER.REPRODUCTION PROHIBITED. Plans to use are all about the same Base: 3,228 global developers. Source: Forrester Analytics’ Business Technographics Developer Survey, 2018 23% 22% 25% 25% 26% 22% 25% 24% 28% 31% 33% 33% 39% 40% Serverless architecture Loosely coupled architecture Microservices Containers Cloud resident development environment Functional programming DevOps Currently Use Plan to use Which of the following processes … does your company currently use/plan to use in the next 12 months?
• 5.
  5© 2018 FORRESTER.REPRODUCTION PROHIBITED. Serverless adoption is just beginning 14% 16% 21% 22% 24% 26% 28% 30% 31% 35% 42% Serverless compute infrastructure/ functional pipeline service Mobile back end Social Message queuing Application-level caching Content management Development tools/IDE Storage Relational database Compute containers Compute virtual machines Base: 1,637 global developers who developed software for a cloud computing environment. Source: Forrester Analytics’ Business Technographics Developer Survey, 2018 Which of the following public cloud-based services has your team developed on/with, on a regular basis?
• 6.
  Definitions and considerations Whatis it, and is it really different from what you’re doing today?
• 7.
  So what doesit mean to be “serverless”? “Serverless is an approach to development that removes their need to care about servers: provisioning, setting up, configuring, or otherwise interacting with them. Beyond that, the name connotes a new architectural approach and operating principles.” “Demystifying Serverless Computing”, Jan 2018, Forrester Research
• 8.
  Is serverless actuallya change from what you do today?
• 9.
  Is serverless areal change? Yes, legitimate changes to how you think about software. • New development approach. Tightly scoped, event-driven, composable pieces. • New operational approach. Little to no infrastructure management, zero consumption during idle periods, fully metered billing. • New business opportunities. Return your team’s focus to business logic, build and utilize marketplaces, quickly stitch together cloud- based systems.
• 10.
  Serverless applies toyour existing priorities. Microservices Functions are one realization of the microservices pattern. It’s a natural fit for many APIs too. DevOps Teams organize around functions and focus on running their function- infused services. Continuous delivery Get code to production quickly. Decomposed systems mean regular updates. Event-driven architecture Adopt a reactive, push- based model that’s foundational to functions. Mobile computing Functions lend themselves to things like notifications and gracefully handling bursty lookups. AI/ML Increasingly, functions look like an option for training models or using models for fast results.
• 11.
  11© 2018 FORRESTER.REPRODUCTION PROHIBITED. Serverless architectures vs. earlier approaches Source: “Demystifying Serverless” Forrester report.
• 12.
  12© 2018 FORRESTER.REPRODUCTION PROHIBITED. The elements of a serverless platform Source: “Demystifying Serverless” Forrester report.
• 13.
  The landscape todayis … fragmented. AWS Lambda Microsoft Azure Functions Google Cloud Functions Auto0 webtask CloudFlare Workers Hosted function-as-a-service platforms Serverless Framework Spring Cloud Function Frameworks for building and deploying functions Knative Apache OpenWhisk Kubeless OpenFaaS Fission Fn Installable platforms
• 14.
  There are things towatch out for. Be excited, but understand the immaturity in the market • How are you going to connect functions together into a system? • What to do with existing software that’s neither event-driven or decomposable into functions? • How do you monitor and trace a mesh of functions? • What’s the right way to track dependencies and keep functions secure? • How are your datastores co-evolving to deal with more ephemeral, stateless services? • Where should you couple to proprietary cloud services versus find something portable? • What ”works” when you have a dozen functions, and collapses when you have 250?
• 15.
  Use cases andPivotal Function Service When to use serverless, and what is PFS offering?
• 16.
  Three categories ofuse cases Event-based Integration ● Scheduled tasks, ETL ● File processing e.g. images and videos ● Complex Event Processing and Change Data Capture ● Monitoring, notifications and alerting ● Custom auth e.g. via API Gateway Large Scale Data Processing ● e.g. pyWren map/reduce ● IoT streams ● Log ingestion ● Machine Learning ● Stateful Stream Processing Web Events ● Website back-end services like form post handlers ● Back-end data services for mobile and web apps e.g GraphQL ● Webhook handlers ● CI/CD automation ● Chat integrations ● Digital assistant services e.g. Alexa skills
• 17.
  Google Cloud Next- July 2018 Community-driven ecosystem of Sources, Channels, Functions, Invokers, BuildTemplates, etc. Kubernetes BuildTemplates Channels CLI Invokers CLI Invokers Build Topics Betting our Faas Future on Knative
• 18.
  riff on Knative Wehave re-architected the riff core, collaborating on a new pub/sub design for Knative. ★ New riff CLI ★ Installs Knative ★ Uses Knative serving, build, and eventing ★ Provides in-cluster builds with buildpacks
• 19.
  Functions as anew developer abstraction Developers are responsible only for the business logic. Dependencies in base image layers can be managed independently. • simpler • more secure • more efficient Function Invoker Function Code Container Base Image Function Layer
• 20.
  Functions subscribe toevent sources through channels Pub/sub channels provide loose coupling. Enable message consumers and producers to operate without prior knowledge of each other. Enable a rich set of patterns beyond request/reply E.g. reactive streams. Publish to Subscriptions Messaging Service Channel Function Function Svc
• 21.
  Pivotal's commercially supported distributionof riff + Knative. Preview release 2018 General Availability TBD
• 22.
  Call to Action ●Check out the latest Forrester research on serverless computing ● Download and try out project riff ● Start using Spring Cloud (Stream and Function) ● Watch videos from recently-concluded SpringOne Platform: ○ Knative, riff, and Pivotal Function Service (keynote) ○ Spring, Functions, Serverless, and You ○ Building Responsive Systems with Serverless, Event-driven Java ○ Securing Spring Functions By Breaking In
• 23.
  Transforming How TheWorld Builds Software © Copyright 2017 Pivotal Software, Inc. All rights Reserved.