AWS Compute Blog
Tag: contributed
Using the circuit-breaker pattern with AWS Lambda extensions and Amazon DynamoDB
The circuit breaker pattern is a powerful tool for helping to ensure the resiliency and stability of serverless applications. Lambda extensions are a good fit for its implementation, as demonstrated in this example.
Running code after returning a response from an AWS Lambda function
This blog shows four ways of combining synchronous and asynchronous tasks in a Lambda function, allowing you to run tasks that continue running after the function returns a response to the client.
Accelerating workflow development with the TestState API in AWS Step Functions
The TestState API helps developers to iterate faster, resolve issues efficiently, and deliver high-quality applications with greater confidence. By enabling developers to test individual states independently and integrating testing into their preferred development workflows, it simplifies the debugging process and reduces context switches.
Automating chaos experiments with AWS Fault Injection Service and AWS Lambda
This blog post details how to run chaos experiments for serverless applications built using Lambda. The described approach uses Lambda extension to inject faults into the execution environment. This allows you to use the same method regardless of runtime or configuration of the Lambda function.
Building a serverless pipeline to deliver reliable messaging
This post is written by Jeff Harman, Senior Prototyping Architect, Vaibhav Shah, Senior Solutions Architect and Erik Olsen, Senior Technical Account Manager. Many industries are required to provide audit trails for decision and transactional systems. AI assisted decision making requires monitoring the full inputs to the decision system in near real time to prevent fraud, […]
Comparing design approaches for building serverless microservices
Developers often move from single responsibility functions to the Lambda-lith when they architectures demand it, but both approaches have relative trade-offs. It’s possible to have the best of both approaches by dividing your workloads per read and write operations.
Introducing the .NET 8 runtime for AWS Lambda
This post is written by Beau Gosse, Senior Software Engineer and Paras Jain, Senior Technical Account Manager. AWS Lambda now supports .NET 8 as both a managed runtime and container base image. With this release, Lambda developers can benefit from .NET 8 features including API enhancements, improved Native Ahead of Time (Native AOT) support, and […]
Re-platforming Java applications using the updated AWS Serverless Java Container
This post is written by Dennis Kieselhorst, Principal Solutions Architect. The combination of portability, efficiency, community, and breadth of features has made Java a popular choice for businesses to build their applications for over 25 years. The introduction of serverless functions, pioneered by AWS Lambda, changed what you need in a programming language and runtime […]
Build real-time applications with Amazon EventBridge and AWS AppSync
Directly invoking AWS AppSync GraphQL API targets from EventBridge simplifies and streamlines integration between these two services, ideal for notifying a variety of subscribers of data changes in event-driven workloads. You can also take advantage of other features available from the two services.
Invoking on-premises resources interactively using AWS Step Functions and MQTT
Accessing on-premises resources with workers controlled via Step Functions using MQTT and AWS IoT Core is a secure, reactive, and cost effective way to run on-premises jobs. Consider updating your hybrid workloads from using inefficient polling or schedulers to the reactive approach described in this post.