Operations | Monitoring | ITSM | DevOps | Cloud

December 2020

Mike Rahmati: My Serverless journey with Cloud Conformity

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.

Dashbird Round-Up 2020

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.

Passing the "Is it Working?" Test with Serverless Architectures Is Not Enough

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.

Dashbird app got a facelift!

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.

AWS Well-Architected and Serverless: Performance Efficiency

And just like that – welcome to the last part in our “Well-Architected and Serverless” series. We hope it’s been informative, insightful, and fun for you, to explore the five pillars of the AWS Well-Architected Framework (WAF) with us! Read the previous posts: Part 1: Security Pillar Part 2: Operational Excellence Pillar Part 3: Reliability Pillar Part 4: Cost Optimization Pillar So let’s look into the last – Performance Efficiency (PERF) – pillar.

6 quick ways to cut cost on your Lambdas

We’ve talked about how serverless architecture is a great option for companies that are looking to optimize costs. Just like with all app building and developments, monitoring the performance of your implementation is crucial and we, the folks at Dashbird, understand this need all too well – this is why we’ve spent the better part of the past year and a half to create a monitoring and observability solution for AWS Lambda and other Serverless services.

Log-based monitoring for AWS Lambda

Monitoring and analytics have been an issue for Serverless systems since they were invented. While it’s easy to attach an agent like NewRelic or DataDog to a server or container, function monitoring requires a different approach. Serverless applications, where logic is distributed over a large number of functions, attaching agents or wrappers leads to cost increase and development overhead.

AWS Well Architected Framework in Serverless: Cost Optimization

This is part four of the “Well-Architected Serverless” series. In this post, we’ll talk about the Cost Optimization (COST) pillar of the Well-Architected Framework (WAF). Part 1: Security Part 2: Operational Excellence Part 3: Reliability The COST pillar concerns itself with the money you spend on your cloud infrastructure. It’s important to think about your system’s cost because, in reality, the perfect system won’t be used simply because it’s too expensive.

How to Build, Deploy, and Debug a Food Delivery App on AWS

The serverless technology feels as exciting and challenging as it was deploying our first app to the internet, seeing it come to life, work and also crash a lot. The latter happening more than we wanted at the begging, but later, when we managed to overcome that challenge, we felt like we could do anything. Depending on the interests, we could focus more on our code and leave that task of deploying, monitoring, and giving support for the apps to the DevOps guys.