Tag: patterns
All the articles with the tag "patterns".
-
Why AI Coding Tools Are Getting Cheaper: Prompt Caching Explained
Updated:Prompt caching discounts repeated input, but the savings depend on exact prefix reuse, model-specific retention, and enough reads to repay each cache write.
-
Prompt Caching Is a Harness Design Problem, Not Just an API Toggle
A 186-request test shows why cache savings depend on stable tools, deterministic prefixes, deliberate breakpoints, routing keys, and measurement inside the agent harness.
-
Building AI Voice Agents with Amazon Nova Sonic and LiveKit: Patterns, Architecture, and a RAG Latency Surprise
Patterns that held up across a series of Nova 2 Sonic + LiveKit voice agents, a telephony architecture that took a real phone call, and a latency finding that contradicts the standard advice on voice RAG.
-
Web Search as a Managed Connector: Wiring Amazon Bedrock AgentCore WebSearch Into Any Agent
Amazon Bedrock AgentCore WebSearch is a managed MCP connector, not a search-API wrapper: an Amazon-operated index with zero data egress, IAM-authorized so there are no secrets to rotate, and $7 per 1,000 queries confirmed on the bill.
-
I Pointed an AI Code-Security Tool at My Own Control Plane
Corridor reviews AI-generated code inside the coding loop instead of after commit. I imported a real AWS control plane, planted an IDOR bug in a PR, and watched what it caught.
-
What Actually Gets Stored When You Put a Vector in S3 Vectors
A vector store keeps three things per record — a key, an array of floats, and a bag of metadata. Your document text is stored as metadata, and a 2 KB limit on the filterable part is what quietly breaks ingestion.
-
Which Tier Does Your Vector Workload Live On?
Amazon S3 Vectors dropped the entry cost of vector storage on AWS to near zero. The question that matters now is which tier of the cost/latency curve your workload sits on — and why agents belong on the cheap one.
-
How AgentCore Gateway Turns Any API Into an Agent Tool
AgentCore Gateway is a managed front door between agents and tools. It handles inbound auth, outbound auth, and protocol translation once, so any API or Lambda becomes an MCP tool that every connected agent can call. Here is how the wiring actually works.