At Lumigo. we believe in serverless technology, and our mission is to make serverless development easy and fast. For the past few months, we’ve been extending our observability and debugging capabilities, making it a breeze for developers to understand the end-to-end story of every request that goes through the system, find the root causes of issues and be able to easily address them.

Today we are announcing an additional $29 million in funding to help Lumigo grow and provide the same powerful observability capabilities we brought to serverless to other cloud-native technologies, including containers and Kubernetes. Lumigo was founded by Aviad Mor and me a few years ago because we believed the world would be rapidly moving to cloud-native architectures and that these technologies are transformative. Our goal was to create the tools that help developers realize this vision.

Here’s a quick roundup of the newest product features, resources, and events from Lumigo.

AWS just announced support for AWS Lambda functions powered by AWS Graviton2 processors. These are 64-bit Arm-based processors that are custom built by AWS and offer a better price to performance ratio. In this post, let me take through what we have learnt about this new option and what it means for you.

Here is a quick round up of the newest product features, resources, and events!

AWS Step Functions is a powerful orchestration service that lets you model even the most complex business workflows. It packs a great visualization tool (which you can also use to design your workflows visually now!) and can integrate with many AWS services directly, including Lambda, DynamoDB, and API Gateway. It’s one of my favorite AWS services and I often use it to model complex or business-critical workflows.

Ideally, observability should help you understand the state of your application and how it performs under different circumstances. However, while serverless observability may seem similar to serverless monitoring and testing, the three achieve different goals. Testing helps you check your application for known issues, and monitoring helps you evaluate system health according to known metrics. Observability helps you search and discover unknown issues, providing end-to-end visibility.

AWS announced AWS Lambda Extensions back in October 2020 and I wrote extensively about it at the time – what it is, how it works, and why you should care. In short, Lambda Extensions allow operational tools to integrate with your Lambda functions and run either in-process alongside your code or in a separate process. To better understand the problems they solve and their use cases, please read my previous article.

This piece was originally three different blogs but is now one. In this piece, we lay out three ways you can improve your AWS Lambda performance. So much has been written about Lambda cold starts. It’s easily one of the most talked-about and yet, misunderstood topics when it comes to Lambda. Depending on who you talk to, you will likely get different advice on how best to reduce cold starts.

Here at Lumigo, we are focused on helping customers succeed with serverless and make it easier for them to build and run serverless applications in production. We love serverless and operate one of the largest serverless systems out there as we ingest and process billions of events from our customers. One thing many customers have asked us for help with is to identify misconfigured resources or places where they can improve by following best practices.