30 Days Of AWS (Day 12)

Welcome back guys, Another update in this crazy challenge. I have good news I finished this course :D

So, the last topic was Lambdas. I know about this service because at work we use it a lot, but every time you can learn new things.

Lambdas

From the official's docs "AWS Lambda is a serverless compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic or create your own back-end services that operate at AWS scale, performance, and security. AWS Lambda can automatically run code in response to multiple events, such as HTTP requests via Amazon API Gateway, modifications to objects in Amazon S3 buckets, table updates in Amazon DynamoDB, and state transitions in AWS Step Functions".

Some benefits of using lambdas:

1. You can build your own backend code, you are the owner and you deploy in the language that you want.

2. You can connect lambdas with another like SQS, SNS or something.

3. Automatic scaling, AWS Lambda invokes your code only when needed and automatically scales to support the rate of incoming requests without requiring you to configure anything.

4. You can coordinate multiple AWS Lambda functions for complex or long-running tasks by building workflows with AWS Step Functions.

5. AWS Lambda allows your code to securely access other AWS services through its built-in AWS SDK and integration with AWS Identity and Access Management (IAM). AWS Lambda runs your code within a VPC by default.

6. With AWS Lambda you pay only for the requests served and the compute time required to run your code.

AWS Lambdas in the real world

You can use lambdas in thousands of different ways, but let me show you how I can use it at work, It's the basic one.

So, when the user requests our endpoint API GW invokes the lambda but how the process is asynchronous, the user gets a response. At the same time, the lambda is processing the information sent by the user, when it finishes, it sends a message to an SNS and another lambda to process with another business logic.

As you can see, the business logic is distributed in the lambdas, because we have conditions and other stuff, that can awake a lambda depending on the condition.

So that was all that this course offers related to lambdas, I know (Thanks to my every day) that I can use lambdas for a lot of things, also it's a great idea when you are using CloudWatch to monitor the health of your service.

The next post will be something like a checkpoint, because this challenge has changed a little bit, besides to clarify a couple of things related to the certification.

That's all for today, thanks for reading I really appreciate that.

for any doubt or suggestion leave a comment.

Thank you.

Comments

[Helen Anderson]

Thanks for sharing your learning and the real world examples as you've been studying.

Hope your study is going well :)

[Wilfredo Pérez]

Thank you for reading. Unfortunately, I didn't finish the challenge because I was pretty busy with personal things, but I have a couple of posts interesting related to AWS that I will post ASAP.

Again thanks for reading.