AWS Architecture Blog
Category: Amazon DynamoDB
Build a unified AI agent architecture with DynamoDB and Bedrock
With native vector search in Amazon DynamoDB, you can store vector embeddings alongside your operational data in a single table. This post shows how to build a unified AI agent architecture where an Amazon Bedrock agent uses one DynamoDB table for both structured lookups and semantic search, with a DynamoDB Streams pipeline that keeps embeddings in sync.
Consistency is the new latency: AI at the data layer
As AI agents move from chatbots to taking action, their reliability depends on the consistency of the data layer beneath them. This post examines how replication lag poisons an agent’s context and shows how to match Amazon Aurora, Amazon DynamoDB, and Amazon Keyspaces replication models to each task’s consistency requirements.
Build a multi-tenant configuration system with tagged storage patterns
In this post, we demonstrate how you can build a scalable, multi-tenant configuration service using the tagged storage pattern, an architectural approach that uses key prefixes (like tenant_config_ or param_config_) to automatically route configuration requests to the most appropriate AWS storage service. This pattern maintains strict tenant isolation and supports real-time, zero-downtime configuration updates through event-driven architecture, alleviating the cache staleness problem.
Build priority-based message processing with Amazon MQ and AWS App Runner
In this post, we show you how to build a priority-based message processing system using Amazon MQ for priority queuing, Amazon DynamoDB for data persistence, and AWS App Runner for serverless compute. We demonstrate how to implement application-level delays that high-priority messages can bypass, create real-time UIs with WebSocket connections, and configure dual-layer retry mechanisms for maximum reliability.
How Karrot built a feature platform on AWS, Part 1: Motivation and feature serving
This two-part series shows how Karrot developed a new feature platform, which consists of three main components: feature serving, a stream ingestion pipeline, and a batch ingestion pipeline. This post starts by presenting our motivation, our requirements, and the solution architecture, focusing on feature serving.
How UNiDAYS achieved AWS Region expansion in 3 weeks
In this post, we share how UNiDAYS achieved AWS Region expansion in just 3 weeks using AWS services.
From virtual machine to Kubernetes to serverless: How dacadoo saved 78% on cloud costs and automated operations
In this post, we walk you step-by-step through dacadoo’s journey of embracing managed services, highlighting their architectural decisions as we go.
Build an enterprise API management solution using Amazon API Gateway
This blog post shows how you can use Amazon API Gateway—along with AWS Lambda, Amazon DynamoDB, and other AWS services—to create a comprehensive and customizable APIM solution. This solution addresses the complex requirements of large enterprises managing APIs at scale.
Top Architecture Blog Posts of 2024
Well, it’s been another historic year! We’ve watched in awe as the use of real-world generative AI has changed the tech landscape, and while we at the Architecture Blog happily participated, we also made every effort to stay true to our channel’s original scope, and your readership this last year has proven that decision was […]
Let’s Architect! Serverless developer experience in AWS
Accelerate your serverless feedback loop with game-changing AWS developer tools: generate tests with AI, visualize DynamoDB schemas locally, optimize Lambda memory, and more—all within a streamlined local IDE experience.









