Recently, I saw a video from a really great developer and YouTuber, Ben Awad, where he discussed Serverless not make any sense. Even though I really enjoyed the video, I am not sure if the author’s points about serverless are entirely valid, and I want to discuss them in this article.
At first glance, all serverless monitoring services seem similar and aim to solve the same problems. However, in Dashbird, we have made decisions that fundamentally differentiate us from our competitors since day one. Over time, those differences have magnified and we have found increasing confirmation and confidence in our approach. Dashbird product strategy is based on three core pillars.
One problem that pops up quite frequently when people try to build serverless applications with AWS API Gateway and AWS Lambda is Execution failed due to configuration error: Malformed Lambda proxy response. There is nothing worse than generic error messages that don’t tell you anything you need to fix the problem, right? And AWS isn’t particularly known for its error message design, if you can even call it that, let alone for giving you the means of fixing the problem.
In this article, we’ll be discussing everything you need to know about the basics of AWS Lambda error handling and some popular methods using StepFunctions and X-Ray. Regardless if you’re an AWS Lambda expert or if you’re a new Lambda user, there’s always something new to learn.
Among all the new features and services that AWS announced during the re:Invent 2020, my favorites were definitely the AWS Lambda updates. And there were many! For example, your code execution is no longer rounded up to the nearest 100ms of duration for billing — you are now billed on a per millisecond. On top of that, AWS increased the Lambda’s memory capacity to 10 GB, and correspondingly the CPU capacity up to 6 vCPUs.
We all know that debugging serverless is time-consuming and hard and that AWS Console doesn’t make it much easier. CloudWatch isn’t quite known for its ease of use. Why? Well to start with, it has suboptimal search features, logs scattered across multiple buckets and groups, little visualization capability, and no structure of Lambda function invocations.
Mike Rahmati is the Head of the Advisory Board at Dashbird. He is the Co-Founder and CTO of Cloud Conformity (acquired by Trend Micro) – a Cloud Security Posture Management Solution – one of the largest and earliest adopters of serverless. Mike is also an active AWS Community Hero. In this article, he shares his journey and experience with serverless. Cloud Conformity was founded in 2014 as a result of our own experience of issues migrating to the cloud.
It’s safe to say that 2020 has been quite the year for everyone, and at Dashbird we’ve had quite a few changes of our own. It became the year full of improvements, growth, and feature releases that we had only imagined a year ago. This is our round-up of all the feature releases we launched this year. Just starting out with Dashbird? Great, you are in the right place.
Say you are an awesome developer sitting contentedly at your desk when a Slack message suddenly interrupts your peaceful mental flow: It would appear there is a data issue with the new Activity History service released last month… Or at least a couple people think there is. Now, instead of making progress on new tasks, you now need to drop those and look into what’s happening here. Sigh.
Today, we launched a new and improved version of Dashbird’s main screen – a single pane of glass, designed to give you an overview of the most important events and metrics across your serverless environment. During the past year, we have invested heavily into building the next stages of our platform, expanding our offering to include services like API Gateway, SQS, DynamoDB, Step-Functions, ECS, and Kinesis, with many more coming in the next months.
