The document discusses serverless architectures and compares them to traditional architectures like monoliths, 3-tier, and microservices. It defines serverless as having functions that are triggered by events to execute code without needing to manage servers. Serverless architectures offer benefits like automatic scaling, pay-per-use billing, and not needing to manage servers directly. However, they may increase complexity for large systems and have limited runtime options currently. Examples of serverless use cases and platforms are also provided.

1. Serverless
Architectures
RANGANATHAN BALASHANMUGAM
@ran_than

2. “What Is The Output
Of Software?”

3. What Is Software Design?
SRC: HTTP://WWW.DEVELOPERDOTSTAR.COM/MAG/ARTICLES/REEVES_DESIGN.HTML
JACK W. REEVES - 1992
—- IN 3 SLIDES —-

4. THE FINAL GOAL OF ANY ENGINEERING ACTIVITY IS SOME TYPE OF
DOCUMENTATION
WHEN THE DESIGN EFFORT IS COMPLETE,
THE DESIGN DOCUMENTATION IS TURNED OVER TO THE
MANUFACTURING TEAM.
SRC: HTTP://WWW.DEVELOPERDOTSTAR.COM/MAG/ARTICLES/REEVES_DESIGN.HTML

5. “GIVEN THAT SOFTWARE DESIGNS ARE RELATIVELY EASY TO TURN OUT
AND
ESSENTIALLY FREE TO BUILD, AN UNSURPRISING REVELATION IS THAT
SOFTWARE DESIGNS TEND TO BE INCREDIBLY LARGE AND COMPLEX.”
SRC: HTTP://WWW.DEVELOPERDOTSTAR.COM/MAG/ARTICLES/REEVES_DESIGN.HTML

6. “SOFTWARE MAY BE CHEAP TO BUILD,
BUT IT IS INCREDIBLY EXPENSIVE TO DESIGN.”
SRC: HTTP://WWW.DEVELOPERDOTSTAR.COM/MAG/ARTICLES/REEVES_DESIGN.HTML

7. “SIMPLIFICATION IS THE TECHNOLOGY TREND FOR 2016.”
- WERNER VOGEL, CTO @ AMAZON

8. “THE BIRTH OF ANY BREAKTHROUGH TECHNOLOGY HAS A TENDENCY TO SPARK FIERCE DISCOURSE.”
@auth0

9. Evolution Of Architectures

10. Monolith
SRC: AWS

11. 3-tier
PRESENTATION
LOGIC
DB
IMAGE SRC: AWS

12. 3-tier - Evolved
SRC: HTTPS://READ.ACLOUD.GURU/SERVERLESS-THE-FUTURE-OF-SOFTWARE-ARCHITECTURE-D4473FFED864#.KOX11S8OH

13. Service Oriented Architecture
SRC: AWS
Presentation Tier Logic Tier
Data Tier

14. Microservices Architecture
SRC: AWS

15. DATA CENTER PAASIAAS SERVERLESS!
ABSTRACTS:
HOSTING
ENVIRONMENT
ABSTRACTS:
PHYSICAL HARDWARE
ABSTRACTS:
OS
ABSTRACTS:
LANGUAGE
RUNTIME

16. BARE METAL CONTAINERSVIRTUALIZATION SERVERLESS!
HIGH
LOW
• Operational costs
• Time to deploy
• Maintenance

17. Serverless?

18. Serverless?

19. “UPLOAD YOUR CODE AND RUN YOUR FUNCTIONS.”

20. What Is Serverless? - Simpler
• Functions
• Functions => Runtimes
• Events trigger functions
• Functions execute on demand
• Infra costs are only by execution
• Continous scaling
• Servers are not developers
responsibility

21. “THE ESSENCE OF THE SERVERLESS TREND IS THE ABSENCE OF
THE SERVER CONCEPT DURING SOFTWARE DEVELOPMENT.”
@auth0

22. “MY STORY - FIXING THE FRAMEWORK”

23. Serverless On Aws
• API gateway.
• Lambda.
• S3 - static content.
• Dynamo DB to persist data.
• Other resources.

24. MICROSERVICES
MONOLITH
What About Microservices?
MICROSERVICES
MICROSERVICES
MICROSERVICES
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION

25. What About Microservices?
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION
FUNCTION

26. MICROSERVICE
What About Microservices?
FUNCTION
FUNCTION
FUNCTION
FUNCTION
API GATEWAY

27. MICROSERVICE
What About Microservices?
FUNCTION
FUNCTION
FUNCTION
FUNCTION
API GATEWAY

28. “Focus On Functions”

29. Function - Expectations
• Do one thing
• Idempotent
• Finish fast

30. GOOGLE CLOUD
FUNCTIONS
AWS LAMBDA
MICROSOFT AZURE
CLOUD FUNCTIONS
Platforms
IRON.IOIBM OPENWHISK

31. Frameworks
KAPPA

32. Google Cloud Functions
• https://cloud.google.com/functions/
docs/tutorials/

33. Microsoft Azure Cloud Functions
• https://azure.microsoft.com/en-us/
services/functions/
• Demo

34. IBM OpenWhisk

36. Iron.IO
SRC: IRON.IO

37. Amazon AWS Lambda
Amazon S3
DYNAMICSTATIC

38. Why Serverless?
• As developer, you may just need to
respond to events with some functions.
• From 24/7 running servers to pay per
function execution.
• Easy configuration and deployment.

39. Why NOT Serverless?
• As Microservices, if the system grows,
complexity grows. Managing 1 server is
better than, managing 500 functions.
• Early stage, limited tools and
monitoring.
• As of now, only fewer languages/
runtimes are supported.
• Local/Offline testing
• Vendor lock???
• Stateless servers

40. USE CASES

41. A Cloud Guru social learning
SRC: HTTPS://READ.ACLOUD.GURU/SERVERLESS-THE-FUTURE-OF-SOFTWARE-ARCHITECTURE-D4473FFED864#.KOX11S8OH

42. Instant - The serverless startup
SRC: HTTPS://BLOG.INSTANT.CM/A-CASE-STUDY-OF-TELETEXT-IO-THE-SERVERLESS-STARTUP-C1E08022BDC2#.H6QH2EA2C

43. Instant - Architecture
SRC: HTTPS://BLOG.INSTANT.CM/A-CASE-STUDY-OF-TELETEXT-IO-THE-SERVERLESS-STARTUP-C1E08022BDC2#.H6QH2EA2C
• Authentication: Google JS, AWS
Cognito
• Editing text: API Gateway
• Handling the drafts: Lambda
• Storing drafts: DynamoDB
• Serving live content: S3 and CloudFront
• No Devops
• No scaling issues
• Pay for usage, not uptime

44. Url Shortner

45. What Is Serverless? - In A Slide
• Functions
• Functions => Runtimes
• Events trigger functions
• Functions execute on demand
• Infra costs are only by execution
• Continous scaling
• Servers are not developers
responsibility
• Platforms: AWS Lambda, Google
cloud functions, Azure functions, IBM
Openwhisk, iron.io
• Frameworks: serverless.com, apex,
webtask, sparta, kappa, deployd,
iopipe

46. “THE BIRTH OF ANY BREAKTHROUGH TECHNOLOGY HAS A TENDENCY TO SPARK FIERCE DISCOURSE.”
@auth0

47. THANK YOU
https://twitter.com/ran_than