Serverless Best Practices with AWS Lambda PowerTools

For one-off tasks, AWS Lambda really can be incredibly easy. You write a few lines of code, deploy it, and you have a function running in the cloud ready to respond to events, scale automatically, and that only costs you pennies.But as your application grows, so does some necessary complexity. When a few one-off functions become a full serverless backend architecture made up of interconnected services, you’ll need to pay careful attention to best practices to ensure that your application is easy to debug, maintain, and scale.That’s where AWS Powertools for Lambda fits in. It’s a suite of reusable utilities designed to simplify bringing best practices around things like logging, tracing, metrics, idempotency and more to your Lambda functions with minimal effort.This demo session will dive into some of the functionality provided by the AWS Powertools (TypeScript) core libraries, such as:Encapsulating best practices into reusable libraries for structured logging, metrics collection, idempotency, and more.Leveraging Middy middleware to integrate common cross-cutting concerns, such as injecting Lambda context or automatically flushing metric.Enabling local testing with LocalStack, allowing you to deploy and debug Lambda functions with structured logs, trace data, and embedded metrics.Providing modular examples that can be deployed to AWS or LocalStack with ease, enabling developers to explore libraries.

Related Talks

How to save state in LocalStack?

LocalStack is ephemeral, so when you stop and restart it, all data is lost. You can use certain features to save the state & load it back when you restart LocalStack. This includes saving the local state for S3 buckets, DynamoDB tables, RDS databases and more. In this video, we explore three mechanisms that allows you to save state in LocalStack. They are:• Persistence• State Export & Import• Cloud Pods ## Documentation• State management: https://docs.localstack.cloud/user-guide/state-management/ • Cloud Pods: https://docs.localstack.cloud/user-guide/state-management/cloud-pods/ • Persistence: https://docs.localstack.cloud/user-guide/state-management/persistence/ • State Export & Import: https://docs.localstack.cloud/user-guide/state-management/export-import-state/

Watch recording

LocalStack Neptune development with G.V() — Gremlin IDE

We’re partnering with gdotv to simplify development with our Amazon Neptune cloud emulator component. You can now easily query, visualise and model your graph data either interactively or using the Gremlin querying language with G.V() - Gremlin IDE.With G.V(), you can considerably enhance your graph database development experience whilst gaining access to a powerful reporting and visualisation toolset for your production data. With LocalStack’s core cloud emulator, parity is ensured between a local Neptune instance and AWS’s own, meaning Gremlin queries in your development environment will behave identically on Amazon Neptune. In this video we demonstrate how to use G.V() with LocalStack Neptune.Read the announcement blog here: https://blog.localstack.cloud/2024-06-05-localstack-neptune-development-with-gv-gremlin-ide/

Watch recording

Towards a LocalStack Snowflake emulator—develop your data pipelines locally!

About a year ago we have released the first version of LocalStack Extensions: Extensions are a powerful mechanism to plug additional functionality into LocalStack - ranging from additional service emulators, to value-add features like Chaos Engineering, request logging, cloud resource replication/proxying, and more.Over the last couple of months we have been experimenting with a LocalStack Snowflake emulator extension, which allows to develop and test your Snowflake data pipelines entirely on your local machine!In this talk, Waldemar discusses and demonstrates how you can develop your Snowflake data pipelines locally with LocalStack.

Watch recording

Launch yourself in the world of local cloud development

Try for free

Talk to Sales