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.
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.
Though the volume of serverless talks is lower this week, the quality and impact lacked nothing. Two must-see presentations emerged highlighting important practices for succeeding with serverless in the enterprise.
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.
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.
This blog post was written jointly by the teams at Lumigo and Cloudway. It’s a step-by-step guide to AWS Step Functions workflows with full monitoring and troubleshooting capabilities. We will use the “right to be forgotten” GDPR workflow as an example application.
The first keynote is over, the talks have started, and the AWS Heroes all got to feel motion-sick but appreciated in their AWS-supplied VR helmets. Good one Tom Here are my week 1 thoughts: Throughout the keynote it was clear that serverless is here to stay. One detail stood out to me above all others: Nearly half of all new compute workloads in Amazon in 2020 were Lambda based. During Andy Jassy’s keynote, a veritable wall of major customers that use Lambda.
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.
Today, AWS announced another major feature to the Lambda platform: the option to package your code and dependencies as container images. The advantage of this capability is that it makes it easier for enterprise users to use a consistent set of tools for security scanning, code signing, and more. It also raises the maximum code package size for a function to a whopping 10GB.
