Operations | Monitoring | ITSM | DevOps | Cloud

Too often serverless is equated with just AWS Lambda. Yes, it’s true: Amazon Web Services (AWS) helped to pioneer what is commonly referred to as serverless today with AWS Lambda, which was first announced back in 2015. But in 2020, it’s important for enterprises to understand that the serverless landscape is much bigger with more opportunities. Serverless is sometimes (narrowly) defined as just being about functions-as-a-service, but that’s a very limited viewpoint.

Serverless applications, due to their distributed nature, are often stuck having to reinvent the wheel. While small utility scripts and functions are often easily instrumented and monitored, anything of a transactional nature will need to implement special code to provide developers with common tools like stack traces, atomicity, and other patterns that rely on a singular flow of control.

The seamless scaling and headache-free reliability of a serverless application architecture has become compelling to a broad community of cloud specialists. But for those who have yet to become converts, a specific issue related to service startup latency—Cold Starts—has been one of the cited key objections. Fortunately, the serverless marketplace is maturing.

Two years ago, I wrote a similar post on Microsoft Flow: How to pass the SQL data table results in a Markdown-formatted table into an Email notification or Approval Requests. It is still quite up to date, i.e., it is an excellent solution that you can still use today. The only problem with that article is that I was using “send an email” action in Power Automate Outlook connector that is currently deprecated.

Next in our series on the Amazon Builders’ Library, Mike Roberts of Symphonia picks out the key insights from the article Going faster with Continuous Delivery by AWS senior manager of software development Mark Mansour.

I’d like to take a moment to point out some of my favorite things that have come across my Twitter timeline in the last week, if you’d like to see more follow Stackery on twitter!

You know what they say: successful deploys are all alike; every unsuccessful deploy is unsuccessful in its own way (ok, no one actually says that, except engineers who have read way too much Russian literature, ahem).

In Part 2 of this series, we looked at how Amazon’s built-in monitoring services can help you get insights into all of your AWS Lambda functions. In this post, we’ll show you how to use Datadog to monitor all of the metrics emitted by Lambda, as well as function logs and performance data, to get a complete picture of your serverless applications. In this post, we will: Datadog integrates with AWS Lambda and other services such as Amazon API Gateway, S3, and DynamoDB.