No matter the metric, serverless is definitely gaining interest. It’s the dream of every developer, supplying the ability to deploy services in the cloud in no time, automatically scale them, enjoy automagic management by a cloud provider—and, most important, keep it all cost effective! How does this dream become a reality? This session covered what serverless is all about and the benefits of running your apps in the serverless environment. It covers the monoliths-microservices-functions progression and when, where, and why to use serverless architecture and how Project Flogo fits in to the overall picture

1. Serverless Integration, Powered by Flogo and Lambda

2. • Developer Advocate
• Passionate about
Serverless, Containers
and all things Cloud
• I love cheesecake, dad
jokes, and APIs
Who am I?
Leon Stigter, Developer Advocate
( @LeonStigter)

3. Who’s a developer? Ops?

4. • Going from Monoliths to Microservices to Functions
• What is serverless all about and why do I care?
• When, where and why use serverless
Key Takeaways

5. • Going from Monoliths to Microservices to Functions
• What is serverless all about and why do I care?
• When, where and why use serverless
Key Takeaways

6. 9
Some time ago, we had
monoliths...
Let’s Take a Trip Down Memory Lane

7. 10
<XML>
<XML>
Let’s Take a Trip Down Memory Lane

8. 11
REST JSON
Fast Binary
Encodings
Let’s Take a Trip Down Memory Lane

9. 12
Let’s Take a Trip Down Memory Lane

10. They Build Apps in Different Ways
ESB
…From building and
connecting monolithic
applications to each
other…
App App App
…To an infrastructure on which modern
applications are built, with API and event-
driven microservices patterns, to support
digital transformation needs
Technically the strategy must “integrate integration” and
blur the lines between development and integration
-Randy Heffner, Forrester Research
Service Service
Service
API
EVENT
API
EVENT
API
API
“App”
Function
Function

11. Is This Your Data Center?

12. But...
Devs wanna dev…

13. • Going from Monoliths to Microservices to Functions
• What is serverless all about and why do I care?
• When, where and why use serverless
Key Takeaways

14. Never Manage Servers
Serverless Is Grounded on a Simple Basis

15. No servers
to manage
or
provision
What Does Serverless Mean?

16. No servers
to manage
or
provision
Scale with
usage
What Does Serverless Mean?

17. No servers
to manage
or
provision
Scale with
usage
Fault
Tolerance
and
Availability
built in
What Does Serverless Mean?

18. No servers
to manage
or
provision
Scale with
usage
Fault
Tolerance
and
Availability
built in
Never pay
for idle
What Does Serverless Mean?

19. 53% of
respondent
s say it is
critical for
their job
Note: Survey done by Serverless Inc. data is available on https://serverless.com/blog/2018-serverless-community-survey-huge-growth-usage/
Is Serverless Really That Important?

20. 53% of
respondent
s say it is
critical for
their job
About 26%
of survey-
takers
were using
2 or more
cloud
providers
Note: Survey done by Serverless Inc. data is available on https://serverless.com/blog/2018-serverless-community-survey-huge-growth-usage/
Is Serverless Really That Important?

21. 53% of
respondent
s say it is
critical for
their job
About 26%
of survey-
takers
were using
2 or more
cloud
providers
Top-3
languages
for
serverless
are
Node.js,
Python and
Go
Note: Survey done by Serverless Inc. data is available on https://serverless.com/blog/2018-serverless-community-survey-huge-growth-usage/
Is Serverless Really That Important?

22. 53% of
respondent
s say it is
critical for
their job
About 26%
of survey-
takers
were using
2 or more
cloud
providers
Top-3
languages
for
serverless
are
Node.js,
Python and
Go
82% of
respondent
s answered
that they
used it at
work
(nearly
double
from last
year)Note: Survey done by Serverless Inc. data is available on https://serverless.com/blog/2018-serverless-community-survey-huge-growth-usage/
Is Serverless Really That Important?

23. With containers you can build,
package, deploy and scale your
apps
Did Someone Say Containers?

24. But Let’s Go One Level Deeper

25. Amazon API
Gateway
Amazon SQS
Amazon
DynamoDB
Amazon
Kinesis
Amazon S3
Amazon SNS
But Let’s Go One Level Deeper

26. Event Source Function Services (Anything)
AWS Lambda™
- Java
- Node.js
- Python
- Golang
- C#
What is in a Function?

27. Amazon API
Gateway
Amazon SQS
Amazon
DynamoDB
Amazon
Kinesis
Amazon S3
Amazon SNS
This is Where Flogo Fits Perfectly

28. Flogo is serverless integration
This is Where Flogo Fits Perfectly

29. © Copyright 2000-2017 TIBCO Software Inc.

30. 91%
of developers use the same
OSS tools for work and
personal projects
98%
of developers use open
source tools at work
96%
of commercial applications
already use open source
software as a component
Numbers Don’t Lie: Open Source Trends

31. Project Flogo
Open Source Stack for Event-Driven Apps
10-50x lighter than
Java, .NET or Node.js
100% Open Source
Stack for all things
event-driven
Common core for all
event-driven
capabilities
Deploy as serverless
functions, containers or
to IoT edge devices
Machine Learning
Project Flogo®

32. How Small Does It Get?
Java Node.js Flogo
180MB
74MB
<10MB
0
50
100
150
200

33. Integration Flows
Microgateway
Stream Processing
New
Process streams of
events inline and infer on
it using Google
Tensorflow
Contextual Rules
New Apply declarative
contextual business
rules
Lightweight
microgateways and API
proxies
Integration flows – deploy
on device or as serverless
functions

34. Mule
Fuse
450+Open source extensions
100+Project Contributors
Flogo is the most
popular open
source integration
project

35. How Can I Build Apps? Flows…
Zero code, Web UI
Golang APIElegant JSON DSL

36. Flogo® Core
Event-driven App Kernel for Serverless & IoT Edge
⚡
Powerful event-driven
programming model based
on triggers and actions
Internal channel for action
chaining. Bundle all app
needs into a single bin
Common contribution model
enabling you to leverage
100s of activities & triggers
Simple interface to extend
event processing capabilities

37. 40
Triggers, Handlers & Actions…
Handle
r
Trigger(s)
Handle
rHandler
Action
Action
Action
App
Events
App = Trigger(s) + Actions(Activities)
Triggers
• receive data from external sources.
• are managed by a configurable
threading model
• have a common interface enabling
anyone to build a Flogo trigger.
Handlers
• dispatch events consumed by
triggers
Actions
• process events in a manner
suitable with the implementation
• have a common interface enabling
unique event processing
capabilities

38. Action Chaining
Handler
Trigger(s) WriteDBLog
WebSocket
Rule 1
Rule 2
Stream Rules Integration
App
Aggregat
e
Filter

39. • Going from Monoliths to Microservices to Functions
• What is serverless all about and why do I care?
• When, where and why use serverless
Key Takeaways

40. 43
It makes life easier (even if it
is just a little bit)
Benefits of Using Serverless

41. Even if it is just mine…

42. Or Yours…

43. Building backend APIs
Data processing
Integrate systems
Note: Survey done by Serverless Inc. data is available on https://serverless.com/blog/2018-serverless-community-survey-huge-growth-usage/
Some Common Use Cases

44. Building backend APIs
Data processing
Integrate systems Build internal tools
Chat bots
IoT appsNote: Survey done by Serverless Inc. data is available on https://serverless.com/blog/2018-serverless-community-survey-huge-growth-usage/
Some Common Use Cases

45. 49
Project Flogo® on AWS Lambda
10¢ for 1.5M Requests
Note: Uses public pricing available for AWS Lambda on https://aws.amazon.com/lambda/pricing/ and based on all kinds of Flogo functions that run within the minimum 128MB
memory and 100 ms billing duration. Estimated paid pricing based on public pricing from AWS Lambda
Rethink Cloud Economics

46. 50
A Cloud Guru
$580 per month for 6.5M
requests per day!
Rethink Cloud Economics

47. • Going from Monoliths to Microservices to Functions
• What is serverless all about and why do I care?
• When, where and why use serverless
Key Takeaways

48. @LeonStigter
Slides or Questions?