Tired of managing servers or paying rent for them whether they are being used or not? Learn about Serverless Architectures that let you build distributed, full-fledged web sites, applications, APIs in a fashion where you don't have to worry about managing servers or even paying for servers.

1. SERVERLESS
ARCHITECTURES
Aditya Challa
thinkadi@outlook.com
thinkadi @thinkadi369
thinkadi

2. WHAT IS SERVERLESS?
• It is a cloud computing execution model.
• The cloud provider dynamically manages
the allocation of machine resources.
• Pricing is based on the actual amount of
resources consumed by an application,
rather than on pre-purchased units of
capacity.

3. CLOUD CHARACTERISTICS
Elastic On-demand Metered

4. IT’S NOT LIKE THERE ARE NO SERVERS AT ALL…
• Serverless does not mean
there are no servers.
• The Server Management
and Capacity Planning
Decisions are hidden from
the developer or operator.

5. SERVERLESS SERVICES
AWS
Lambda
COMPUTE $ 0.20 per million executions
$0.000000208 per 100ms
Amazon
S3
(Simple Storage
Service)
STORAGE $ 0.023 per GB Storage
0.090 per GB Transfer
$0.004 per 10,000 GET requests
$0.005 per 1,000 PUT requests
Amazon
DynamoDB
DATABASE $ 0.25 per GB Storage
0.090 per GB Transfer
$0.00065 per Write Capacity Unit / hr
$0.00013 per Read Capacity Unit / hr
$0.02 per 100,000 DynamoDB Streams
read request units

6. SERVERLESS SERVICES
DNS $0.50 per hosted zone / month
$0.400 per million queries
API
GATEWAY
$ 3.50 per million calls
0.090 per GB Transfer
CDN 0.085 per GB Outbound Transfer
$0.020 per GB Inbound Transfer
$0.01 per 10,000 requests
Amazon
Route 53
Amazon
API
Gateway
Amazon
Cloudfront

7. SERVERLESS SERVICES
QUEUES $ 0.40 per million requests
0.090 per GB Transfer
PUB/SUB $ 0.50 per million requests
0.090 per GB Transfer
TRANSCODING $0.030 per minute for HD Video
$0.015 per minute for SD Video
$0.0045 per minute for Audio
Amazon
SQS
Amazon
SNS
Amazon
Elastic
Transcoder

8. SERVERLESS
ARCHITECTURE
PRINCIPLES

9. SERVICE, NOT SERVER
• Use a compute service, not
server.
• Execute code on demand,
isolated, independent and
often granular.
• Assume all operations as
stateless.

10. SINGLE-PURPOSE FUNCTIONS
• Dissect your application into
multiple functions.
• Apply the Single
Responsibility Principle (SRP)
to each function.
• Stateless, Reusable, Granular
with well-defined interface.

11. EVENT-DRIVEN PIPELINES
• Minimize synchronous
operations (where the user
or another function is
waiting)to bare minimum.
• Use asynchronous, push-
based pipelines as much as
possible.

12. THICK, POWERFUL FRONTENDS
• Terminate Serverless
functions as quick and early
as possible.
• Move some of the heavy
lifting to the front-end.
• Build rich clients that can
interact with services
directly.

13. EMBRACE THIRD PARTY SERVICES
• Reduce custom code by
bringing in third party
services that add value.
• Look for third party services
that are also serverless.

14. LET’S BEGIN…

15. STATIC WEBSITE
Amazon
S3
STATIC CONTENT
(.html, .js, .css, .jpg, .gif, .ico, etc.)
Bucket:
example.com
example.com
example.com
example.com.s3.amazonaws.com
Amazon
Route 53

16. STATIC WEBSITE WITH CONTACT US FORM (EMAIL)
example.com
example.com.s3.amazonaws.com
api.example.com
d#####.cloudfront.netAmazon
Route 53
Amazon
API
Gateway
AWS
Lambda
POST /contact-us
processContactUsForm
api.example.com
api.example.com
Amazon
S3
STATIC CONTENT
(.html, .js, .css, .jpg, .gif, .ico, etc.)
Bucket:
example.com
example.com
Third Party Email
Service (SendGrid)

17. STATIC WEBSITE WITH CONTACT US FORM (DB)
Amazon
DynamoDB
example.com
example.com.s3.amazonaws.com
api.example.com
d#####.cloudfront.netAmazon
Route 53
Amazon
API
Gateway
AWS
Lambda
POST /contact-us
processContactUsForm
api.example.com
api.example.com
Amazon
S3
STATIC CONTENT
(.html, .js, .css, .jpg, .gif, .ico, etc.)
Bucket:
example.com
example.com

18. E-COMMERCE APPLICATION
Amazon
S3
Amazon
Route 53
example.com
d#####.cloudfront.net
STATIC CONTENT
(.html, .js, .css, .jpg, .gif,
.ico, etc.)
Bucket:
example.com
api.example.com
d#####.cloudfront.net
Amazon
API
Gateway
Amazon
DynamoDB
GET /orders
readOrders
readOrderById
GET /orders/{id}
POST /orders
createOrder
updateOrder
PUT /orders/{id}
api.example.comexample.com
AWS
Lambda
Amazon
Cloudfront

19. E-COMMERCE APPLICATION
(SERVER-SIDE RENDERING)
Amazon
Route 53
static.example.com
d#####.cloudfront.net
STATIC CONTENT
(.js, .css, .jpg, .gif, .ico,
etc.)
api.example.com
d#####.cloudfront.net
Amazon
API
Gateway
Amazon
DynamoDB
GET /orders
readOrders
readOrderById
POST /orders
createOrder
updateOrder
api.example.com
Amazon
API
Gateway
example.com
example.com
d#####.cloudfront.net
GET /orders
renderHTML
api.example.com
static.example.com
AWS
Lambda
AWS
Lambda
GET /orders/{id}
PUT /orders/{id}
Amazon
S3
Bucket:
static.example.com
Amazon
Cloudfront
GET
/orders/{id}

20. NANOSERVICES
Amazon
Route 53
api.example.com
d#####.cloudfront.net
Amazon
API
Gateway
GET /orders
readOrders
api.example.com
combineOrdersAndP
roducts
Amazon
DynamoDB
Orders
Table
readProducts
Amazon
DynamoDB
Products
Table

21. THICK CLIENTS (S3)
Amazon
API
Gateway
POST /images
api.example.com
createImageId
AndUploadUrl
Amazon
Route 53
images.example.com
images.example.com.s3.amazonaws.com
api.example.com
d#####.cloudfront.net
Amazon
DynamoDB
Images
Table
Amazon
S3
PUT /{url}
Bucket:
images.example.com
images.example.com
1 2

22. THICK CLIENTS (S3 AND DB)
Amazon
API
Gateway
POST /images
api.example.com
createDBCredentials
AndUploadUrl
Amazon
Route 53
images.example.com
images.example.com.s3.amazonaws.com
api.example.com
d#####.cloudfront.net
Amazon
DynamoDB
Images
Table
Amazon
S3
PUT /{url}
Bucket:
images.example.com
images.example.com
1 3
2

23. EVENT-DRIVEN
PIPELINE
Amazon
S3
PUT /{url}
Bucket:
images.example.com
images.example.com
markImageAsUploadedA
ndSendForVirusCheck
Amazon
SQS
Virus Scan
Server picks
messages
requesting to
scan.
Virus Scan
Server finishes
the scan and
sends back a
notification.
Amazon
SNS
Amazon
DynamoDB
Images
Table
resizeImageAndMarkAsP
rocessed
Amazon
DynamoDB
Images
Table
Amazon
S3
Bucket:
images.example.com
1
2
3
4 5
678
9

24. EVENT-DRIVEN
TRANSCODING
Amazon
S3
PUT /{url}
Bucket:
videos.example.com
videos.example.com
markVideoAsUploadedA
ndSendForVirusCheck
Amazon
SQS
Virus Scan
Server picks
messages
requesting to
scan.
Virus Scan
Server finishes
the scan and
sends back a
notification.
Amazon
SNS
sendVideoFor
Conversion
Amazon
DynamoDB
Videos
Table
Amazon
S3
Bucket:
videos.example.com
1
2
3
4 5
678
Amazon
Elastic
Transcoder
9
Amazon
DynamoDB
Videos
Table
markVideoAsProcessed
11
10

25. DB STREAM-BASED EVENTS
Amazon
API
Gateway
POST /orders
api.example.com
createOrder
Amazon
DynamoDB
Orders
Table
processPayment
1
Amazon
DynamoDB
Stream
2
3
Third Party Payment
Service (Stripe)
processOrderAnd
MarkAsProcessedOrF
ailed
sendEmail
4
5
Amazon
DynamoDB
Stream
6
dispatchProcessedOr
derTo
DeliveryDepartment
Amazon
SQS
7a
sendToAnalytics
7b
Amazon
SQS
sendToRetry
Payment
7c
Amazon
SQS
Third Party Email
Service (SendGrid)

26. TIME-BASED EVENTS
readOrders
purgeOrdersOlder
Than6Months
Amazon
DynamoDB
Orders
Table
deleteOrders
ById
Run At
1 AM
everyday
1
2

27. WATCH OUTS
• Not for everyone or every organization.
• Not a silver bullet to every problem.
• Undesirable Service Levels due to cold services.
• Investment in extra efforts to keep services warm.
• No control of the underlying hardware or operating
system.
• Vendor Lock-In
• Decentralization means lot of extra initial work.

28. SELLING POINTS
• No hassle of maintaining or even paying for servers.
• Pay for only what you really use.
• Scalability and Flexibility
• Statelessness
• Less Code Complexity
• Fast and Easy Testability due to Isolation

29. THANK YOU
Please contact Aditya Challa thinkadi@outlook.com
with any questions or serverless projects you may need help with.