With AWS Lambda, we get scalability and resilience out-of-the-box. What’s more, AWS also provides built-in monitoring, logging and tracing support through CloudWatch and X-Ray. These built-in tools provide a good starting point but many developers eventually outgrow them as their serverless application becomes more complex. In this post, let’s take a serverless application and see how Dashbird can help you debug a serverless application.

Even in this field of work, not everything can be perfected 100%. There are always some situations and cases that will force you to go back or even remain in the present spot, despite your wish to keep going forward at your own pace. In this article, we’ll talk about the cold start impact on latency. What is it? How to fight against it? Is there a successful way of avoiding it or not?

The high-level steps for implementing chaos experiments involve: defining your application’s steady state, hypothesizing the steady state in both the control and experimental groups, injecting realistic failures, observing the results, and making changes to your code base/infrastructure as necessary based off of the results.

AppDynamics’ new serverless agent for AWS Lambda helps our customers running serverless microservice workloads gain visibility and insight into the performance and impact of their applications.

Since the beginning of Dashbird, we’ve been conducting user interviews with all the users that take the time to jump on a call with us. One of the most common requests we get is the ability to customise alerts - specifically, what failures you will get notified upon and the ability to set custom alert based on metrics. Today we announce a new part of Dashbird that takes care of that - an incident management platform.

A few months back, I blogged about my experience arriving at Stackery after code school. Months later, each day is still interesting and challenging and I’m so glad to have decided to pursue serverless as my concentration. I credit my AWS certifications for narrowing my focus enough to lead me to this point. The serverless community puts so much emphasis on exploration and getting started on your work or experiments today that, getting some exposure to AWS, you can get started right away.

What a year! It started with just me and Mikk, hacking away at our homes with an MVP and a handful of customers. Now, Dashbird is a team of 6 people with a lot of customers, global investors and a vision for the future. Looking back at the year, we’ve had a lot of wins and also our fair share of failures/learning experiences. I’m very excited for the upcoming year, but before we get into that, let’s look back at the year that just ended.

It’s the beginning of a new year and when it comes to computing, going serverless is the resolution of many engineering teams. At Stackery, this excites us because we know how significant the positive impacts of serverless are and will be. So much, in fact, that we’re already thinking about its applications for next year and beyond.