The Serverless Revolution: an brief discussion of how Reckon is using AWS Lambda and the Serverless Framework to drive innovation

1. The Serverless Revolution
Toby Hede
Head of Architecture

2. Accounting, Business &
Bookkeeping Software

3. Architecture and Stuff

4. Artist’s Impression
Information including artists impressions and computer generated images does not in any part constitute any form or offer of contract; it is
provided as a guide only and has been provided in good faith and with due care.

5. A brief history of clouds

6. There is no cloud.
It’s just someone else’s computer
Zen
Proverb

7. 1946
Electronic Numerical Integrator And Computer
ENIAC

10. 2006
Amazon launches EC2

11. Artist’s Impression
Information including artists impressions and computer generated images does not in any part constitute any form or offer of contract; it is
provided as a guide only and has been provided in good faith and with due care.

12. 2014
Amazon launches AWS Lambda

13. Artist’s Impression
Information including artists impressions and computer generated images does not in any part constitute any form or offer of contract; it is
provided as a guide only and has been provided in good faith and with due care.

14. THIS IS A REALLY BIG
DEAL

15. A brief history of web apps

17. Not so fast

20. Backend-as-a-Service
Functions-as-a-Service
Serverless

21. Backend-as-a-Service

22. 3rd party
mobile-centric
data storage
messaging
and stuff

25. Functions-as-a-Service

26. event-driven
ephemeral
fully managed
stateless compute containers

27. independently deployed
transparently provisioned
billed per request

29. Serverless

30. FaaS
+/- BaaS
+/- SaaS

31. Super Advanced Cloud

32. Microservices?

33. Architectures

34. Compute as glue

36. Compute as backend

38. Immutable Architecture

40. Everything is Architecture

41. DevOps

42. Serverless
the framework
not
the paradigm

47. 150 lines
of
JSON

49. 270 lines
of
JSON

52. Testing

57. GraphQL

60. Contingency Plans

63. Swagger

64. Bleeding Edge

65. You will get hurt

66. Avoid over-engineering

67. Maybe try a server

68. The End
visit us at reckon.com

69. Cue the live demo

70. Cue the failure
of the live demo
as required