Loading…
Topic
834 posts about Architecture. Every summary links to the original.
See the idea
Amazon Bedrock is the managed reasoning tier in an agent architecture, not the whole system. This layered view shows the pipelines, governed tables, query layer, and guardrails around it.
API versioning as an architecture: requests enter through a version header, pass through a chain of reversible version changes, and reach controllers that only ever see the latest model.
BIAN gives banks a shared vocabulary and service-domain contracts that sit between business concepts and the systems implementing them. See how domains, contracts, and governed access stack into one architecture.
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
Transactional and analytical databases serve different workloads: OLTP handles high-volume, real-time reads and writes with ACID guarantees, while OLAP supports complex queries over large historical datasets for reporting and business intelligence. The comparison focuses on trade-offs involving latency, concurrency, data freshness, schema design, transaction size, and storage format. Row-oriented storage and normalized schemas support precise operational updates, whereas column-oriented storage and denormalized designs improve compression, scans, and aggregations across millions of rows. The source describes transactional systems as foundational for applications such as banking, e-commerce, healthcare, and reservations, while analytical systems support dashboards, forecasting, and ad-hoc analysis. Its recommended architecture is to run both systems independently and connect them with Change Data Capture, balancing operational reliability with analytical throughput.
A global payment processor migrating 382 AWS accounts between AWS Organizations encountered control-plane failures when AWS Resource Access Manager automatically severed organization-bound resource shares. Although data planes continued operating for shared resources such as AWS Transit Gateways, infrastructure automation lost the ability to modify dependencies like AWS Glue Data Catalog databases. The engineering team resolved this by implementing temporary retained bridge shares, establishing external principal associations that survived cross-organization account transfers. Following each account move, automated tooling restored durable original shares, validated Lake Formation permissions, and deleted the bridge copies to prevent configuration drift. This bridge-share workflow enabled the migration of 378 accounts before a Transitional Service Agreement deadline without customer downtime.
Generative AI training across hundreds of thousands of GPUs makes the scale-out network a first-order performance bottleneck, because synchronized collectives expose weaknesses in conventional Ethernet. Static ECMP, packet loss controls such as PFC, and slowly tuned congestion control can create stragglers, head-of-line blocking, latency spikes, and multi-tenant interference. Spectrum-X Ethernet addresses these conditions with hardware-accelerated adaptive per-packet routing, targeted ECN- and RTT-based congestion control, and a SuperNIC Plane Load Balancer that distributes traffic across independent network planes. Spectrum-X Multiplane uses shallow two-tier fat trees and host-edge optical devices to provide path diversity while scaling a two-tier design to over 128,000 endpoints. In the cited tests, Spectrum-X sustained 98% of theoretical line rate across GPU pairs, held P99 tail latency to 8–9 microseconds under 75% load, recovered from a link flap in 2.68 milliseconds, and limited bandwidth loss under 10% fabric failure to 11%.
Agentic AI inference has shifted from single-turn requests to long, stateful workflows that reason, invoke tools, coordinate subagents, and reuse growing context, increasing token and power demands. The post presents SemiAnalysis AgentX, an InferenceX benchmark that replays prerecorded Claude Code sessions turn by turn, preserving context, input/output lengths, reasoning time, tool-call latency, and KV-cache pressure while varying concurrency. It evaluates tokens per megawatt alongside E2E normalized interactivity, standard interactivity, E2E latency, and TTFT; NVIDIA-measured Vera Rubin NVL72 results, pending SemiAnalysis review, show up to 30x higher throughput per megawatt than GB300 NVL72 at 160 tokens per second per user. GB300 also delivers up to 15x H200 throughput per megawatt, up to 10x lower cost per million tokens, and roughly 80x higher throughput on Kimi K3 2.8T, supported by MoE runtimes, communication overlap, Dynamo, and NVLink.
Power-constrained AI factories measure efficiency by AI output per watt, because facility overhead, rack losses, and operational inefficiency reduce the power available to compute. In an illustrative 100 MW budget, 60% reaches AI load, while static rack provisioning can strand headroom that another rack could use. NVIDIA DSX MaxLPS addresses this with dynamic power allocation, workload-profile power optimization, and 45° C thermal and site design, including warm-water liquid cooling. Its Dynamic Power Software, currently in Developer Preview, models topology from utility to GPUs and reallocates unused capacity within policy-defined budgets, with optional DSX Exchange integration. For Vera Rubin NVL72, NVIDIA projects up to 40% more Rubin GPU capacity within the same power budget, while validation compares unmanaged and managed runs using throughput, latency, errors, power, utilization, and compliance.
Agentic AI factories connect diverse users, agents, applications, data sources, and storage systems to massively accelerated compute, making dedicated DPU processing essential for line-rate networking, storage, and security. Scale-In evolves north-south access into a coordinated infrastructure domain built with BlueField-4, NVIDIA DOCA, and Spectrum-X Ethernet. BlueField-4 combines programmable control-plane processing with inline data-path engines, a 64-core Grace CPU, LPDDR5X memory, PCIe Gen6 host connectivity, and an 800 Gb/s network interface. The architecture offloads security, tenant isolation, storage protocols, provisioning, and telemetry from host CPUs; the source states that Spectrum-X storage paths can provide up to 1.45x the throughput of off-the-shelf Ethernet, while independent control and observability support more consistent operations as AI infrastructure scales.
Agentic AI fleets must handle unpredictable trajectories in which long sequential reasoning chains are interrupted by short bursts of parallel tool calls, retrieval, sandbox, or sub-agent work. Telemetry from 163,594 sessions found over 97% had unique trajectory profiles, making fleet sizing around several specialized CPU designs impractical; the sequential path is latency-bound while fan-out requires concurrency. It presents NVIDIA Vera CPU as a single balanced design point, combining strong loaded per-core performance, concurrency, memory bandwidth, and a low-latency monolithic architecture, with Olympus cores using a wide front end, branch prediction, and deep out-of-order execution. Using estimated SPEC CPU® 2026 results across four agentic workloads, it reports up to 1.5x the agentic performance of AMD Venice, while noting that Venice figures were estimated from SPECrate® 2026 data and that results may vary.
Serving agentic AI at more than 3,000 output tokens per second while retaining a 100K-token KV cache creates a small-batch tensor-parallelism challenge: fixed communication and coordination costs can offset distributed-compute gains. NVIDIA Groq 3 LPX addresses this with compiler-scheduled execution across 256 LP30 local processing units, 128 GB of collective SRAM, and 96 112-Gbps C2C links per chip, planning transfers before execution and overlapping communication with computation at 320-byte-vector granularity. Artificial Analysis measured 3,431 output tokens per second at 100K context on Gemma 4 31B, and 3,382 tokens per second at 10K context. On SPEED-Bench coding tasks, the same system reached a median 4,767 tokens per second and a P80 of 5,520. The post describes pairing LPX with Vera Rubin NVL72 through prefill-decode, attention-FFN, or external-drafter speculative-decoding configurations for projected large-model agentic workloads.
Deploying the Junie coding agent locally on Apple MacBook M5 hardware requires overcoming steep performance bottlenecks during model execution. Engineers optimized the entire stack using Qwen3.6-27B rather than Qwen3.8-27B, which severely degrades without token-heavy reasoning enabled. At the agent layer, Junie appends requests directly into a rolling context and caches initial prompt prefixes to maximize KV-cache reuse across tasks. For model inference, the team disabled reasoning, selected 4-bit quantization, and patched MLX-VLM to execute self-attention prefill matrix operations using faster 8-bit instructions on the M5 processor. Combining these prefill improvements with simultaneous multi-token prediction and n-gram speculative decoding delivered up to a 2x generation speedup.
Default authentication setups often redirect users to third-party domains and issue generic transactional emails, causing password manager failures, browser cookie restrictions, and perceived phishing risks. To mitigate these issues, teams can configure custom identity domains via DNS CNAME records to preserve origin alignment and session persistence. Developers can also capture custom user fields directly within hosted login prompts using Universal Login partials alongside pre-registration Actions rather than managing custom authentication servers. For transactional messaging, teams must replace rate-limited built-in email tools with dedicated external providers and configure SPF, DKIM, and DMARC records alongside Liquid-templated emails. Managing these configurations through version control and deployment tools maintains security standards without adding excessive infrastructure maintenance overhead.
AI agent architectures on AWS frequently divide operational records and vector embeddings across separate databases, creating synchronization lag and infrastructure overhead. To resolve this fragmentation, a single DynamoDB table can store operational document attributes alongside embeddings by leveraging native vector search. An Amazon Bedrock agent directs incoming queries to AWS Lambda action groups, which run standard CRUD operations or semantic searches against the DynamoDB SearchVectors API. When items change, a DynamoDB Streams pipeline uses Amazon Titan Text Embeddings V2 to generate new embeddings and write them back to the table. This unified approach eliminates standalone vector databases while keeping semantic indexes synchronized with operational updates.
Quantitative strategies need instrument groupings that capture both ordinary co-movement and dependence during market stress, while remaining stable and inexpensive to recompute. The workflow constructs rolling absolute Pearson-correlation and tail pairwise dependence matrices (TPDM), factorizes them with nonnegative SymNMF using AdaptGrow, and derives soft loadings, hard argmax labels, and structural-break diagnostics. A trace-based formulation reduces estimated peak storage from approximately 20n2 to 4n2 bytes, while row-sharded distributed execution communicates O(nk) data; the system uses eigenspectrum-based selection between full-batch and block-stochastic AdaGrad. Across 250 synthetic windows, the setup tests planted membership changes and a joint tail-stress episode: ARI is intended to identify reclassification, whereas TPDM reveals co-crash dependence that ordinary correlation can miss. Reported factorization timings include 13.0 and 12.4 seconds for 100,000 instruments across four GB200 GPUs, and approximately two and four minutes for one million instruments across 64 GPUs on 16 nodes, not end-to-end timings.
Netflix operates over 30,000 Apache Flink jobs across multiple AWS regions, ranging from managed pipelines to complex stateful DAGs. Its initial in-house autoscaler used external telemetry from Mantis and Atlas to scale TaskManagers as a single unit, cutting resource usage by 25–45% but failing on multi-operator stateful topologies. To address these limitations, Netflix adopted the Apache Flink Autoscaler library, which calculates True Processing Rate and per-vertex parallelism using internal metrics. The architecture uses Temporal workflows orchestrated within a Spring Boot application to evaluate jobs individually and prevent cross-job blast radiuses. Implementing the open-source autoscaler reduced annualized compute expenditures by 58% for client telemetry and logging, saving approximately $1.1 million.
As software agents make implementation faster and cheaper, engineering difficulty shifts away from typing code toward defining correctness and verifying behavior reliably. Omitting specifications forces human reviewers into expensive correction loops, while overspecification clutters model context windows with stale prose and competing instructions. To find the optimal middle ground, teams must validate specifications before coding, using one agent to draft minimal constraints and another to attack ambiguities, hidden dependencies, and missing failure modes. Multi-agent architectures demand formal interface contracts, schemas, and executable checks because interpretive drift compounds rapidly across unbounded agent handoffs. Core Extreme Programming and Agile practices such as continuous integration, small release batches, and rapid feedback loops remain essential error-detection mechanisms during agentic development.
NVIDIA’s Agentic Variation Operators (AVO) is a general-purpose agent architecture designed to make frontier language models reliable on extended, multistep tasks. It combines tool use and execution with persistent memory, an iterative inspect-plan-implement-evaluate loop, and a supervisor that can redirect work when progress stalls. In a seven-day GPU-kernel optimization study, AVO explored more than 500 directions, produced 40 committed versions, and outperformed cuDNN by up to 3.5% and FlashAttention-4 by up to 10.5% across evaluated configurations. On the ARC-AGI-3 public set, the same architecture achieved a 100.00 RHAE score across 25 environments, completing all 183 levels in 6,624 actions; the post cautions that comparisons with other systems are not controlled ablations.
The post explains where security controls should sit in an emerging AI agent stack as agents gain capability and operate over longer horizons. It distinguishes behavioral controls in models and harnesses, which guide proposed actions, from authoritative infrastructure controls that bind identity, enforce policy, contain failures, and record activity. The stack is presented as layers for models, harnesses, meta-harnesses, secure runtimes such as NVIDIA OpenShell, and inference infrastructure, with the runtime boundary established before launch so tools, plugins, MCP processes, and delegated runtimes operate under policy. It recommends least privilege, isolation, explicit authorization, auditability, short-lived and task-scoped access, independent checks, and safer failure states, while describing four security profiles from isolated to adversarial workloads. The conclusion is that every high-impact external effect must pass through enforcement layers the agent cannot bypass.
AgentFlo designed an architecture using Amazon Bedrock AgentCore and AWS serverless infrastructure to address traffic spikes and build trust in autonomous commerce agents. Security operates across three stages: AWS Fargate filters prompt injections and opt-outs, AgentCore Gateway enforces deterministic Cedar authorization policies during tool execution, and post-turn privacy filters screen outputs. Session isolation is maintained across merchants through AgentCore runtime microVMs, while AgentCore Observability and Amazon CloudWatch provide end-to-end tracing. Data reliability and long conversation journeys rely on Amazon DynamoDB context storage, Amazon Bedrock Knowledge Bases, and Amazon S3 Vector embeddings. Early deployment data showed a 12 percent net revenue uplift.
Spring Boot externalizes application configuration across files, environment variables, system properties, and command-line arguments to allow a single artifact to run across multiple environments. A resilient setup classifies values into application defaults, deployment configurations, and externalized secrets stored in dedicated vaults. Binding properties to type-safe Java records via @ConfigurationProperties ensures immutability, supports relaxed property mapping, and eliminates the discovery issues common to scattered @Value annotations. Enforcing validation with @Validated and Jakarta Bean Validation constraints triggers fail-fast startup behavior when required settings are absent or malformed. Property precedence determines the effective runtime values, which must be adapted appropriately whether deploying a monolith, containerized workloads in Kubernetes, or a microservices cluster.
Grab designed Jarvis Pro as an AI assistant for account managers turning complex account data into actionable merchant conversations. Early prototypes generated polished but operationally unsound advice, such as pushing promotions when order drops were caused by outlet pauses and fulfillment issues. To address this, the team implemented a "route first, answer later" design that uses a prompted LLM classification step constrained by a routing guide to dictate context, tool paths, answer structure, and guardrails before generation. The pipeline also isolates narrow memory decisions, reconciles metric freshness across data sources, and caps tool calls to maintain usability. In offline evaluations across 351 realistic prompts, routing matched safe routes 99.4% of the time while answer quality scores in a portfolio subset improved from 78.5 to 91.0.
At Salesforce, engineering teams discovered that AI coding agents could produce internally consistent code and passing test suites that still failed to meet actual requirements. To ensure correctness before writing code, the team developed an agentic Spec-Driven Development workflow centered on explicit specifications and gated verification. The system separates evidence-based repository lookups handled by agents from subjective judgment calls escalated to human engineers. Implementation plans must cite repository evidence reviewed by a Skeptic Agent, while a Compliance Matrix traces each success criterion directly to executable test proof. Finally, a multi-agent review system evaluates the implementation under an asymmetric rule allowing an independent judge to downgrade passing checks but never override failed gates.
The best engineering reads, once a week.
