Microservices without Servers

Ashan Fernando

Why Managing Servers is Difficult?• Provision & Manage

VM Instances

• Patching OperatingSystems

• Update Software

• Extra Effort to Handle Failures

Managing a Fleet of Microservices is Hard

What if you can build Microservice without Servers?• Fully Managed• No provisioning• Zero Administration• High Availability

• Developer Productivity• Focus on Code• Innovate rapidly• Reduce time to market

• Continuous Scaling• Automatically• Both Scale Up and Down

Credits: AWS Webniar Series

Lambda – Computation

API Gateway – API Management

S3 – File Storage & Delivery

CloudFront – CDN and Basic Routing

DynamoDB – NoSQL Database

Units of a Serverless Microservice in AWS

Serverless Microservice

Engine behind AWS Microservices• Event-driven Compute Service

• Innovative cost model for Execution Time

• Automatic scaling

• Currently supports• Java, NodeJS & Python

AWS API Gateway Web Console

AWS Lambda Web Console

Using Serverless Frameworkhttps://serverless.com/

Serverless MicroservicesCase Study with Amazon Web Services

• Microservices written in NodeJS

• Web Application built with AngularJS

• Hybrid Mobile App built with Ionic Framework

• NoSQL Database using Amazon DynamoDB

Case Study with AWSSimplified Architecture

Case Study with AWSServerless Microservices & Web App1. Angular App

• Cloudfront• S3

2. Microservices• Cloudfront• API Gateway• Lambda• DynamoDB• SES

Case Study with AWSManaged Microservices (Not Serverless)

• Lambda has its own limits• Cold Start vs Hot Start

• Not fitting some use cases• Services with dependencies

with large libraries• Services with logic operated on

a single, medium to largedataset

• Why Managed Docker?