Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Cloud Native Architectures with an Open Source, Event Driven, Serverless Platform

1,158 views

Published on

IBM keynote at CloudNativeCon / KubeCon in Seattle, Washington on November 8, 2016.
https://cnkc16.sched.org/event/8K4c

New cloud programming models enabled by serverless architectures are emerging, allowing developers to focus more sharply on creating their applications and less on managing their infrastructure. The OpenWhisk project started by IBM provides an open source platform to enable these cloud native, event driven applications.

Daniel Krook, Senior Software Engineer, IBM

Published in: Software
  • Be the first to comment

  • Be the first to like this

Cloud Native Architectures with an Open Source, Event Driven, Serverless Platform

  1. 1. Cloud native architectures with an open source, event driven, serverless platform Daniel Krook, Senior Software Engineer, IBM
  2. 2. @DanielKrookOpenWhisk.org Serverless architectures are drawing interest due to a combination of compelling technical and business factors
  3. 3. @DanielKrookOpenWhisk.org With serverless developers focus more on code, less on infrastructure Bare metal Virtual machines Containers Functions Decreasing concern (and control) over stack implementation Increasingfocusonbusinesslogic
  4. 4. @DanielKrookOpenWhisk.org Serverless platforms can address 12 Factors for developers I Codebase Handled by developer (Manage versioning of functions themeselves) II Dependencies Handled by developer, facilitated by serverless platform (Runtimes and packages) III Config Handled by platform (Environment variables or injected event parameters) IV Backing services Handled by platform (Connection information injected as event parameters) V Build, release, run Handled by platform (Deployed resources immutable and internally versioned) VI Processes Handled by platform (Single stateless containers used) VII Port binding Handled by platform (Actions or functions automatically discovered) VIII Concurrency Handled by platform (Process model hidden and scales in response to demand) IX Disposability Handled by platform (Lifecycle hidden from user, fast startup and elastic scale prioritized) X Dev/prod parity Handled by developer (Developer is deployer. Scope of what differs narrower) XI Logs Handled by platform (Developer writes to console.log, platform streams logs) XII Admin processes Handled by developer (No distinction between one off processes and long running)
  5. 5. @DanielKrookOpenWhisk.org Emerging workloads are a good fit for event driven programming Execute app logic in response to database change Perform edge analytics in response to sensor input Provide cognitive computing via a conversational bot Schedule tasks according to a specific timetable Invoke autoscaled mobile backend services
  6. 6. @DanielKrookOpenWhisk.org New cost models can more accurately charge for compute time Applications billed by compute time (millisecond) rather than reserved memory (GB/hour). While many applications must still be deployed in an always on model, serverless architectures provide an alternative that can result in substantial cost savings for a variety of event driven workloads. Means a greater linkage between cloud resources used and business operations executed.
  7. 7. @DanielKrookOpenWhisk.org Technological and business factors make serverless compelling Serverless architectures are gaining traction Cost models getting more granular and efficient Growth of event driven workloads that need automated scale Platforms evolving to facilitate cloud native design for developers
  8. 8. @DanielKrookOpenWhisk.org OpenWhisk enables these serverless, event-driven workloads Serverless deployment and operations model Optimized utilization, fine grained metering at any scale Flexible, extensible, polyglot programming model Open source and open ecosystem (Apache proposal) Ability to run in public, private, and hybrid models OpenWhisk a cloud platform that executes code in response to events
  9. 9. @DanielKrookOpenWhisk.org Developers work with triggers, actions, rules, and packages Data sources define events they emit as Triggers. Developers map Actions to Triggers via Rules. Packages provide integration with external services. T A P R
  10. 10. @DanielKrookOpenWhisk.org Try OpenWhisk on IBM Bluemix bluemix.net
  11. 11. @DanielKrookOpenWhisk.org OpenWhisk is built on solid open source foundations bit.ly/ow-int
  12. 12. @DanielKrookOpenWhisk.org Join us to build a cloud native platform for the future! OpenWhisk.org dwopen.slack.com #openwhisk developer.ibm.com/open

×