The document discusses serverless applications using the 'bat-signal' application as a case study, emphasizing characteristics such as no server management, auto-scaling, and precise cost performance. It details two categories of serverless architecture: Backend as a Service (BaaS) and Function as a Service (FaaS), alongside examples and their respective components. The benefits and drawbacks of serverless computing, including cost reduction and vendor lock-in, are also highlighted.

1. Serverless
Applications Running In Their Natural State
Tobias Coetzee
@Tobiascode

2. Bat-signal application
● Automated Bat-Signal Administration
● Tracks Villains & Incidents

3. What is serverless?

4. Five Traits of serverless
No Server Management
Auto-Scales
Precise Costs
Performance Capabilities
High Availability

5. Two Categories of serverless
Backend as a Service
Third-party API-based services that replace
core subsets of functionality in an
application
Function as a Service
Event-driven computing where developers
only deploy functions which are triggered
by events

6. Serverless Origin

7. Evolution of the cloud
Application
Runtime
Containers
(Optional)
Operating
System
Hardware
Functions
Virtualization
InfrastructureasaService
Application
Runtime
Containers
Operating
System
Hardware
Functions
Virtualization
ContainerasaService
Application
Runtime
Containers
Operating
System
Hardware
Functions
VirtualizationPlatformasaService
Application
Runtime
Containers
Operating
System
Hardware
Functions
Virtualization
FunctionasaService
Not our
problem
Our problem
Value Line

8. Bat-Signal App Demo

9. 3-tier architecture
Application Server
Server Application
Data Access Layer
Villain Logic
Notifications
Signal Logic
Villain UI Signal UI
Database Server
Signal Data
Villain Data
Security Data
Security

10. AWSBrowser
Serverless architecture
VillainUISignalUI
Cognito
User&APISecurity
APIGateway
GET|POST|PUT|DELETE
Lamda
VillainCreateAlertReceived
VillainRead
VillainUpdate
VillainDelete
NotifyUser
LogAlert
NotifyBatman
DynamoDb
AlertTableVillainTable
SimpleNotificationService
Pub/SubNotifications
S3

11. Backend as a service

12. Backend as a service Examples
Don’t create another users table again.
Skip the backend and go straight to the
database.

13. AWSCognitoBrowser
Bat-signal application - Baas components
VillainUISignalUI
User&APISecurity
APIGateway
GET|POST|PUT|DELETE
Lamda
VillainCreateAlertReceived
VillainRead
VillainUpdate
VillainDelete
NotifyUser
LogAlert
NotifyBatman
SimpleNotificationService
DynamoDb
Pub/Sub
AlertTableVillainTable
Notifications
S3

14. Function as a service

15. Life cycle of a function
Event
Source
Triggers Function

16. Function as a service Platforms
Hosted Installed

17. AWSCognitoBrowser
Bat-signal application - faas component
VillainUISignalUI
User&APISecurity
APIGateway
GET|POST|PUT|DELETE
Lamda
VillainCreateAlertReceived
VillainRead
VillainUpdate
VillainDelete
NotifyUser
LogAlert
NotifyBatman
SimpleNotificationService
DynamoDb
Pub/Sub
AlertTableVillainTable
Notifications
S3

18. Benefits & Drawbacks

19. benefits
Reduced Cost
Shorter Lead Time
Increased Flexibility
Flexibility in Scaling

20. Inherent drawbacks
Vendor Control
Multitenancy
Vendor Lock-in
Security
Repetition of Logic
Server Optimizations
No In-Server State

21. Thank You
For Staying Till The End
Tobias Coetzee
@Tobiascode