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.

Build a cloud native app with OpenWhisk


Published on

IBM OpenWhisk presentation and demo for developerWorks TV on December 14, 2016.

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.

At this live coding event, Daniel Krook provide an overview of serverless architectures, introduce the OpenWhisk programming model, and then deploy an OpenWhisk application on IBM Bluemix, while you watch, step-by-step.

Daniel Krook, Senior Software Engineer, IBM

Published in: Software
  • Be the first to comment

Build a cloud native app with OpenWhisk

  1. 1. Build a cloud native app with OpenWhisk @DanielKrook • Senior Software Engineer • IBM Cloud
  2. 2. What you will learn today • How serverless technology enables developers to write cloud native applications better, faster, and cheaper. • How OpenWhisk provides an open source platform to enable these cloud native, event driven applications. • How to get started developing with OpenWhisk on Bluemix based on two hands on coding demos
  3. 3. Serverless architectures are drawing interest due to a combination of compelling technical and business factors
  4. 4. With serverless developers focus more on code, less on infrastructure Bare metal Virtual machines Containers Functions Decreasing concern (and control) over stack implementation Increasingfocusonbusinesslogic
  5. 5. 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)
  6. 6. 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
  7. 7. 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.
  8. 8. 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
  9. 9. 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
  10. 10. The OpenWhisk programming model
  11. 11. 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
  12. 12. Triggers A class of events that can occurT Social events Data changes Device readings Location updates User input
  13. 13. Actions Code that runs in response to an event (that is, an event handler) A
  14. 14. Actions Can be written in a variety of languages, such as JavaScript, Python, Java, and Swift A function main(params) { return { message: 'Hello, ' + + ' from ' + }; };
  15. 15. Actions Or any other language by packaging with DockerA
  16. 16. Actions Can be composed to create sequences that increase flexibility and foster reuse A AA := A1 + A2 + A3 AB := A2 + A1 + A3 AC := A3 + A1 + A2
  17. 17. Rules An association of a trigger to an action in a many to many mapping. R R := T A
  18. 18. Packages A shared collection of triggers and actionsP A A read write T changes A translate A forecast A post T topic Open Source A myAction T myFeed Yours T commit Third Party
  19. 19. OpenWhisk in action
  20. 20. The OpenWhisk execution model Pool of actions Swift DockerJS Trigger 1 Running action Running action Running action 3 OpenWhisk Engine 2 A T AAA
  21. 21. Demo 1: Timer triggered action Trigger 1 Running action 2 T A 1. Cron syntax alarm 2. Log the current time $ wsk action create handler handler.js $ wsk action invoke --blocking handler $ wsk trigger create every-20-seconds --feed /whisk.system/alarms/alarm --param cron “*/20 * * * * *” $ wsk rule create invoke-periodically every-20-seconds handler $ wsk activation poll
  22. 22. OpenWhisk enables event driven applications Event Providers Cloudant GitHub Weather … Which triggers execution of associated OpenWhisk action 2 Slack JS Swift Docker … An event occurs, for example • Commit pushed to GitHub repository • Data changed in Cloudant 1 OpenWhisk
  23. 23. OpenWhisk can implement REST microservices Send HTTP request HTTP GET 1 Invoke OpenWhisk action get-customers Browser Mobile App Web App 2 JS Swift Docker … OpenWhisk API Proxy
  24. 24. Demo 2: Polyglot applications with data triggers Trigger 2 JavaScript action 3 T A 1. Image uploaded to Cloudant 3. JavaScript action parses image metadata and transforms image Docker action 4 A incoming checks processed checks 5 1 2. Trigger fired in OpenWhisk 4. Docker action parses image with OCR 5. Extracted info stored back to Cloudant OpenWhisk
  25. 25. More examples: Smart home IoT, mobile banking Project OpenFridge: Improving customer service with event driven IoT Project OpenChecks
  26. 26. Summary
  27. 27. What you learned today • We’re in the early days of an evolution that is empowering developers to write cloud native applications better, faster, and cheaper • OpenWhisk provides an open source platform to enable cloud native, serverless, event driven applications • Bluemix provides a hosted instance of OpenWhisk that you can use to get started (and offers integration with a catalog of services)
  28. 28. Try OpenWhisk in hosted on IBM Bluemix
  29. 29. Join us to build a cloud native platform for the future!