In recent years, the uprise of the cloud has brought us a lot of new and disruptive technologies. Everybody is talking about SaaS, PaaS, IaaS and other sorts of aaS. In 2014, Amazon launched AWS Lambda as the pinnacle of the cloud computing. It allows developers to focus on code, without spending time on managing servers. The goal of this talk is to introduce the serverless architecture style, but it will also contain demos (eg. using AWS Lambda and Google Cloud Functions) on how to make this style work. Expect Lambda functions in NodeJS, using DynamoDB, consuming other functions via the AWS API Gateway. The talk will conclude with best practices on how to use these serverless functions.

1. THE SERVERLESS CLOUD
BART BLOMMAERTS
@DAGGIEBE

2. THE SERVERLESS CLOUD
BART BLOMMAERTS
▸ Application Architect
▸ Ordina Belgium
▸ JWorks
▸ @DaggieBe

3. WHAT?
SERVERLESS

4. IAAS

5. PAAS

6. ▸ Not having a clue
CLUE - LESS

7. ▸ Not having … servers?
SERVER - LESS

8. THE SERVERLESS CLOUD
NO MORE SERVERS ?
▸ Obviously not
▸ Existence of servers is hidden
▸ Applications need to run on something
▸ But …

9. THE SERVERLESS CLOUD
NO MORE WORRIES ?
▸ Well ..
▸ Less server management
▸ No worries about security updates, scalability,
availability, …

10. THE SERVERLESS CLOUD
NO MORE OPS ?
▸ Well …
▸ Specialised, outsourced team
▸ Still need:
▸ Monitoring, deployment, security, networking,
debugging support, memory management, scaling,
configuration, …
▸ Opportunity for tooling!

11. FAAS

12. THE SERVERLESS CLOUD
EVENT-DRIVEN
▸ Can be triggered by many different event types
▸ Depends on cloud provider

13. THE SERVERLESS CLOUD
PAY PER EXECUTION
▸ No running servers
▸ Only consume server time, when executed
▸ Only pay when executed
▸ Small operational cost

14. THE SERVERLESS CLOUD
PAY PER EXECUTION - EXAMPLE (AWS)
REPORT RequestId: da9f321f-c5ff-4a6f-a84b-
e469cbca197d Duration: 0.61 ms Billed Duration:
100 ms Memory Size: 128 MB Max Memory Used: 16 MB

15. THE SERVERLESS CLOUD
SEAMLESS SCALING
▸ No risk of under- or over provisioning
▸ Short-lived “compute containers”
▸ Isolated from other functions
▸ Resources provided from function configuration
▸ Containers can be reused, but do not depend on it. It’s
the suppliers prerogative to create a new one

16. THE SERVERLESS CLOUD
STATELESS
▸ No state is stored between invocations
▸ To preserve state, use
▸ a database
▸ the file system
▸ cross-application cache
▸ …

17. THE SERVERLESS CLOUD
EASIER
▸ Well …
▸ If you want to :)

18. LESS SERVER MANAGEMENT
EVENT-DRIVEN
PAY PER EXECUTION
SEAMLESS SCALING
STATELESS
EASIER

19. SUPPLIERS
SERVERLESS

20. AWS LAMBDA

21. IBM BLUEMIX
OPENWHISK

22. MICROSOFT
AZURE CLOUD
FUNCTIONS

23. GOOGLE CLOUD
FUNCTIONS

24. AUTH0 WEBTASK

25. DEMO
COLLABORATIVE ECONOMY

26. THE SERVERLESS CLOUD
YOUR DATA
▸ Use your data
▸ Publish an API
▸ Enrich existing data

27. THE SERVERLESS CLOUD
YOUR IDEA
▸ Use someone else's data
▸ Combine data
▸ Use data differently
▸ Creativity adds value

28. SERVERLESS
ENABLES
EXPERIMENTATION

30. THE SERVERLESS CLOUD
THE SERVERLESS FRAMEWORK
▸ CLI
▸ Scaffolding
▸ Best practices (grouping of functions)
▸ Lifecycle support (create, deploy, invoke, …)
▸ Soon to be supplier independent
▸ https://serverless.com

31. THE SERVERLESS CLOUD
COLLABORATIVE ECONOMY
▸ Code
▸ https://github.com/bart-blommaerts/serverless-demo
▸ IoT
▸ https://github.com/ordina-jworks/lora-iot-demo

32. BEST PRACTICES
SERVERLESS

33. THE SERVERLESS CLOUD
SUPPLIER CHOICE
▸ Integration
▸ Offering
▸ Tooling
▸ Build and deploy
▸ Monitoring
▸ Execution time is limited
▸ SLA?

34. THE SERVERLESS CLOUD
CODE
▸ Initialize services outside of function
▸ eg. database connection
▸ Limit your function size
▸ Use an external editor

35. THANK YOU
@DAGGIEBE