This presentation gives a 90,000 foot view of serverless application architectures, examining both of the major types of serverless application.

1. An Introduction to Serverless Development
Matt Billock
matt@backand.com

2. ● What is Serverless Development
● Types of Serverless
Development
● Pros and Cons
● What's Available?
Agenda:

3. What is Serverless Dev?
● Replaces the server component with an
API
● Evolution of Containerization,
Microservices
● Supported by many providers
● Focuses on payment for execution,
rather than availability

5. Sole Provider Serverless
● Entire back end is with a sole provider
● Provides central point for integration
● Low integration costs and complexity
due to sole provider
● Varying features and offerings, as well
as lock-in

6. FaaS Serverless
● Backend composed of external services
● Combined behind an orchestration layer
● Fine-grain control over feature
providers
● Higher integration costs, complexity
● Need to maintain tech assets

7. Serverless Benefits
● Reduces operating costs
○ Pay for use, not for presence
● Easy scalability
○ Uses industry-standard platforms
● Resiliency
○ Risks can be spread across
multiple providers.

8. Serverless Cons
● Server customization limited
○ Varies per provider
● Limited feature availability
○ No universal standard feature set
● Higher integration costs
○ Error handling and "glue" code

9. What's Available - Sole Provider
● Backand
● Firebase
● Parse (open-sourced now)
● Others

10. What's Available - FaaS
● Google Cloud Functions
● Microsoft Azure Functions
● AWS Lambda
● IBM OpenWhisk
● Others

11. What's Available - Tools & APIs
● Serverless Framework
● Kong API
● Auth0
● Fugue
● … many, many others

12. THANK YOU
https://github.com/backand
https://www.backand.com
matt@backand.com