The document discusses adopting a serverless architecture to address pain points with a traditional architecture. Specifically, it notes that serverless allows processing without needing to run an always-on EC2 instance, easier management of resources for multiple tenants, lower cost parallel processing without expensive resource allocation, and lower costs overall. The new serverless architecture uses AWS Lambda for offloading analytics data hits from application servers to keep bills low, and uses Lambda functions triggered by SNS topics to send SMS messages through the standard SNS API.

1. Adopting
Serverless
By : Gayan Hewa

2. Traditional Architecture
** Excludes obvious measures like VPC , Multi-AZ etc for simplicity sake

3. Pain points
1. Having required to run at least 1 EC2 instance always to make sure we can
process items as it hits the queue.
2. Managing the config for multiple tenants and ensuring the server has
enough resources to process requests.
3. Parallel processing is expensive in terms of resource allocation
4. Cost

4. New Architecture

5. New Architecture Topic per SMS
driver.

6. Summary
● Offloading analytics data hits to application servers since this is a lot of
data and SNS + Lambda works like charm keeping the bills low ( < $50 )
● SMS Drivers as a Lambda function offer us the ability to send sms’s from
the standard SNS API , only configuration we have done is have a topic
per function.
● Push notification Processing
● Email Processing
● We anticipate to move all worker job’s functions completely to process on
Lambda.

7. Thank you.