cloud native architectures with an open source, event driven, serverless platform

Cloud native architectures with an open source, event driven, serverless platform

Daniel Krook, Senior Software Engineer, IBM

@DanielKrookOpenWhisk.org

Serverless architectures are drawing interest due to a combination of

compelling technical and business factors


With serverless developers focus more on code, less on infrastructure

Bare metal

Virtual machines

Containers

Functions

Decreasing concern (and control) over stack implementation

Incr

easi

ng fo

cus

on b

usin

ess

logi

c


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)


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


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.


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


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


Developers work with triggers, actions, rules, and packagesData sources define events they emit as Triggers.

Developers map Actions to Triggers via Rules.

Packages provide integration with external services.

T

A

P

R


Try OpenWhisk on IBM Bluemix

bluemix.net


OpenWhisk is built on solid open source foundations

bit.ly/ow-int


Join us to build a cloud native platform for the future!

OpenWhisk.org

dwopen.slack.com #openwhisk

developer.ibm.com/open