Serverless Explained with AWS Operational Responsibility Model
In this article, we are going to explain What is Serverless with AWS Operational Responsibility Model.
When we talk about serverless, the best way to explain what serverless is looking to AWS Operational Responsibility Models. You can think this is a spectrum about responsibility level of services. By the end of the article, you have an overall picture of AWS Serverless Services.
I have just published a new course — AWS Lambda & Serverless — Developer Guide with Hands-on Labs.
AWS Operational Responsibility Model
Security and compliance are shared responsibilities between AWS and the customer. Depending on the services deployed, this shared model can help ease the customer’s operations.
If we look at the image above and if we look at the horizontal way, we can see the traditional on-premises machines , virtual machines, bare metal hardware devices at the beginning of the image.
And if we go to right hand side, you can see the cloud infrastructure, which includes managed services that managed application services on the cloud.
If we go the last of the right hand side, you can reach the fully Serverless services that we don’t any responsibility about servers, patches, updates and also not consider about scaling, reliability and availability so on.
And if we look the vertical way, you can see the separation of services:
- Compute
- Databases
- Storage
- Messaging / Application Integrations
- Analytics
and we can put here API Management for AWS API Gateway.
So these are the services by grouping for aws that we mostly use when developing enterprise level applications.
AWS Products on Official Website
You can also see this kind of grouping on https://aws.amazon.com/ and than see Products section:
We can find groups and breakdowns of every AWS Services like
- Application Integrations — SNS, Event Bridge, Step Functions
- Compute —AWS Lambda, EC2
- Database — DynamoDB, Auora Serverless
- Frontend Web — API Gateway
- Serverless — AWS Lambda, DynamoDB, SQS, SNS..
- Storage — S3
- Messaging/Application Integrations — SNS,SQS, EventBridge
- Analytics — Athena
- API Management for AWS API Gateway
So according to these grouping, AWS services evolve by time and now in Serverless part they have very great service which you don’t consider any server management and scalability issues.
Step by Step Design AWS Architectures w/ Course
I have just published a new course — AWS Lambda & Serverless — Developer Guide with Hands-on Labs.
In this course, we will learn almost all the AWS Serverless Services with all aspects. We are going to build serverless applications with using AWS Lambda, Amazon API Gateway, Amazon DynamoDB, Amazon Cognito, Amazon S3, Amazon SNS, Amazon SQS, Amazon EventBridge, AWS Step Functions, DynamoDB and Kinesis Streams. This course will be 100% hands-on, and you will be developing a real-world application with hands-on labs together and step by step.
Source Code
Get the Source Code from Serverless Microservices GitHub — Clone or fork this repository, if you like don’t forget the star. If you find or ask anything you can directly open issue on repository.
