Loading…
Topic
832 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
An AI agent can exfiltrate private data when one session combines access to confidential information, attacker-controlled content, and an external communication channel, even though each capability is individually authorized. Omnigent's contextual policy tracks those three legs as session state: private data, untrusted content, and exfiltration, with human-defined tool or argument-based classifications. It allows ordinary actions until both prerequisite legs are lit, then denies the outbound call that would complete the trifecta. In the support assistant example, a user-supplied ticket instructs the agent to read internal Q3 revenue figures and email them externally; without the policy, the confidential number leaves in a reply, while the protected run blocks that email. A password-reset ticket still proceeds because it lights only the untrusted-content leg, and an empty internal lookup does not light the private-data leg.
Uber’s Payments Platform, internally called Gulfstream, grew from a small 2016 microservices effort into infrastructure supporting $217 billion in annualized gross bookings, nearly twice that amount in total money movement, and ledger balances for more than 1.2 billion entities. It is built around immutable Money Orders, zero-sum double-entry accounting, strongly consistent ledger balances, and three core models: money orders, ledgers, and entity changelogs. Independent stateless services communicate primarily through Apache Kafka, while generic abstractions for lines of business and payment instruments let new products and methods plug into the platform; synchronous in-session flows use Cadence. As scale and audit requirements increased, Uber introduced Entity Fares, addressed hot ledger entities, and built LedgerStore for auditability and tamper-evident record-keeping, while also extending the ledger as a multi-tenant service.
NVIDIA Magpie Multilingual TTS is a 364M-parameter open-weights model for multilingual voice applications, supporting 12 languages, including newly added Modern Standard Arabic, Korean, and Brazilian Portuguese. It is positioned for cascaded voice-agent architectures in which ASR, TTS, and LLM components are independently deployed, tuned, and scaled on controlled infrastructure. Frame stacking predicts two audio frames per decoding step, while a local transformer models dependencies between simultaneously generated codebook tokens; NVIDIA reports 32–79 ms single-stream TTFA across its listed GPUs. Compared with the previous release, French and Spanish CER improved to 1.54% and 0.60%, while SSIM reached 0.747 and 0.793; German SSIM also increased to 0.742. The Hugging Face checkpoint supports research and fine-tuning, while NVIDIA NIM provides optimized production serving and NeMo supports customization.
Cloudflare for Government has achieved FedRAMP Class D (High) certification status, following its FedRAMP Moderate authorization in 2022 and sponsorship by the National Institute of Standards and Technology. FedRAMP High covers systems handling the nation’s most sensitive unclassified data, including law enforcement, emergency services, financial systems, and national security information, where a control breach could be catastrophic. Cloudflare says its offering runs the same software stack and services as its commercial platform on one global network, while its Data Localization Suite ensures traffic inspection and processing for FedRAMP High occur exclusively in U.S. data centers. The systems developed for FedRAMP High are also the foundation of Cloudflare’s stated pursuit of DoD Impact Level 4 authorization, with access to its Zero Trust, application performance, and developer features as they are released.
Netflix designed a query execution serving layer for its Real-Time Distributed Graph to power sub-100ms responses across diverse graph traversal workloads spanning billions of nodes and edges. To prevent compounding network delays in multi-hop queries, the engine uses a breadth-first traversal model that batches entity lookups across entire frontier levels rather than tracing paths depth-first. The entire serving architecture relies on asynchronous composition across small thread pools of 16 to 24 threads, ensuring no thread blocks while waiting on remote storage or enrichment I/O. Selective caching via EVCache targets stable properties with volatility-matched TTLs, producing 70 to 80 percent cache hit rates and reducing backend storage calls by three to four times. A layered filtering hierarchy pushes depth and edge limits directly to the storage tier, eliminating bespoke code changes while isolating system resources against excessive fan-out.
Web traffic increasingly shifts between human interaction and automated agents, rendering point-in-time security checks ineffective against sophisticated automation. Cloudflare addresses this shift through continuous behavioral analysis designed to evaluate trust across entire user sessions rather than relying on static point-in-time hurdles. Its CDN-injected client-side system, Precursor, tracks continuous behavioral indicators like cursor movements to catch mid-session automated takeovers. To counter rapid bot adaptation, Cloudflare is introducing self-adjusting machine learning models under Adaptive Intelligence and non-deterministic defenses such as the AI Labyrinth. These tools allow site owners to poison scraper training data, trap crawlers in synthetic webs, or queue legitimate agents while dynamically penalizing abusive traffic.
Cloudflare launched the beta of Radar Researcher, an AI tool designed to let users explore global Internet traffic data using plain-language queries. Built entirely on Cloudflare's developer platform, the system uses the Cloudflare Agents SDK within a Cloudflare Worker, maintaining conversation state and SQLite databases inside Durable Objects. The inference layer relies on Workers AI running models like Kimi K2.7 through an ordered fallback chain across three model families to prevent outages, routed via AI Gateway for logging, caching, and guardrails. Radar's frontend renders retrieved data using its existing native interactive charts, while smaller dedicated models generate conversation titles and follow-up suggestions asynchronously. Additionally, Radar introduced support for the WebMCP standard, exposing imperative and declarative tools to allow external browser agents to navigate and interact with the platform directly.
Workers AI and AI Gateway are converging into a unified AI control plane to simplify model access, billing, and observability. Developers can now access both services through a single entrypoint using unified Workers bindings and the /ai/ REST endpoint. Specifying a default gateway automatically instruments requests with payload logging, token tracking, and cost attribution without manual dashboard setup. Cloudflare has also rolled out unified prepaid billing, allowing teams to spend AI Gateway credits on Workers AI models while unlocking higher rate limits. Planned future features include model-first routing for automated provider failover and smart routing powered by task classifiers on Workers AI.
GreenMart’s smart-fridge scenario addresses how an agent can turn a detected grocery need into an authorized order without receiving unrestricted access to household card or wallet credentials. GreenMart uses Stripe Agentic Commerce Suite to expose its catalog and checkout through a hosted Agentic Commerce Protocol (ACP) endpoint, while retaining responsibility for inventory, pricing, fulfillment, and order operations. A fridge agent discovers products and creates a checkout, and a companion app evaluates the final checkout against deterministic household rules covering items, totals, delivery, substitutions, and budgets. After approval, Link can provide bounded payment authority, while direct Shared Payment Tokens (SPTs) support lower-level Stripe integrations; virtual cards are described for eligible non-Stripe merchants. The design emphasizes auditable policy decisions, explicit escalation or denial, idempotent retries, webhook reconciliation, and stopping when changes exceed the household’s authority.
Agentic workflows are AI-driven processes that let one or more agents plan, execute, and refine multi-step tasks toward a defined goal with minimal human intervention. Unlike chatbots and fixed automation, they evaluate context and intermediate results at runtime, gather data, select tools dynamically, and adapt when outcomes are incomplete, incorrect, ambiguous, or unexpected. The described pattern combines agents and LLMs with APIs, databases, code executors, prompts, feedback mechanisms, memory and state management, and, for complex work, coordinated specialized agents. Production reliability depends on clear success criteria, action guardrails, human review points for high-stakes actions, audit trails, governance, and production-grade infrastructure. Examples include customer-service resolution, fraud investigation, supply-chain optimization, and event-driven document processing across systems.
Model Context Protocol previously required stateful connections between clients and remote servers, creating operational complexity around sticky sessions, message replay, and open streams. The newly released MCP 2026-07-28 specification transitions MCP to a fully stateless protocol alongside updated SDKs across TypeScript, Python, Go, and C#. The protocol eliminates mandatory handshakes and session identifiers from core request paths while enabling servers to run on request-scoped infrastructure like Cloudflare Workers. Interactive elicitation is restructured through Multi Round-Trip Requests, which allow servers to return input requirements without sustaining persistent connections. Standardized headers for method names and improved OAuth authorization mechanisms further enable standard web infrastructure to inspect and manage MCP traffic efficiently.
The modern web produces billions of bot requests that repeatedly fetch unchanged pages, highlighting an architecture fundamentally misaligned with automated visitors acting on behalf of paying users. Cloudflare outlines an open Agentic Internet structured around four foundational capabilities: readability, discoverability, callability, and payability. Identity and access rely on open specifications such as Web Bot Auth and Private Access Control Tokens, while Markdown for Agents and the Kitesurf browser reduce token overhead and context window bloat. For execution and monetization, WebMCP exposes structured tools directly through the browser, and protocols like x402 paired with Monetization Gateway enable per-fetch transactions. These open standards allow domain owners to define tool contracts, verify bot identities, and monetize agent traffic without relying on legacy advertising models.
Physical Intelligence, which builds robotics foundation models, needed a data stack that could support both transactional operations and high-cardinality analytical workloads. Its previous single RDS Postgres instance could not handle those demands, so the team migrated to ClickHouse Cloud and adopted Postgres managed by ClickHouse for OLTP alongside ClickHouse for OLAP. Postgres is automatically replicated into ClickHouse through ClickPipes, while materialized views, full-text indices, and a query agent help researchers search across the company’s data. The resulting stack supports faster, easier exploration as data volume grows from the 10 billion to 100 billion row range, and also handles telemetry through ClickHouse with ClickStack and Grafana.
Meta’s ads ranking systems process millions of candidates per second under millisecond latency budgets, creating tension between richer sequence models and efficient serving. The post presents a multi-stage architecture that moves long-history user modeling into asynchronous offline transformers, caches user-level embeddings, and combines them with fresh user and ad signals in an online ranking model. Dense tokenization places sparse features and behavioral sequences in one vocabulary, while target-aware multi-head attention learns higher-order interactions between historical behavior and the candidate ad. On real-world ads traffic, performance follows a log-linear relationship with compute across depth, enrichment, width, and sequence length, with balanced growth and diverse sequences identified as scaling levers. Together with broader model innovations, the approach contributed to a cumulative 6% conversion lift on Instagram, 3% on Facebook, and 3.5% lift in Facebook ad clicks, and serves as a core component of GEM.
Salesforce redesigned its internal observability platform, Argus, to eliminate single-region failure risks while ingesting approximately 4 billion metrics per minute. Operating out of a single AWS region previously created a global blast radius and generated high cross-region data transfer costs. To mitigate these risks without the prohibitive expense of full multi-region replication, the engineering team implemented a geo-local architecture that processes and stores telemetry closer to its origin across production geographies. A newly introduced federation query layer relies on Elasticsearch mappings to route queries selectively to relevant regional clusters, avoiding broad fan-out. The platform also adopted metadata caching for wildcard queries and implemented HTTP 206 partial-response handling to maintain visibility when individual regions experience downtime.
The 2026-07-28 Model Context Protocol specification release candidate addresses production bottlenecks caused by the earlier session-oriented HTTP model, including session pinning, sticky routing, lost state, and Redis-backed infrastructure. It removes the initialize/initialized handshake and Mcp-Session-Id, carrying protocol version, client information, and capabilities in _meta on each request while exposing method and name through HTTP headers. The update also introduces ttlMs/cacheScope caching, Multi Round-Trip Requests for elicitations and task progress, issuer and resource-indicator verification, and full JSON Schema 2020-12 support. The post says the stateless core enables ordinary load balancing, serverless deployment, and transparent failover, while SDK beta releases for TypeScript, Python, Go, and C# support migration.
Mercado Libre rebuilt its O11y events observability platform to answer granular business-level questions such as why a payment failed across a large microservice environment. The previous storage-layer design performed transformation, filtering, and aggregation at query time, causing queries to run longer than five minutes and making high-cardinality analysis expensive. The team moved storage to ClickHouse Cloud on AWS while retaining its existing ingestion path, and shifted heavy work into the database with materialized views, layered retention, and a dedicated lookup table for high-cardinality filtering. O11y events uses OpenTelemetry instrumentation with business-flow attributes and samples all traffic for critical applications. The resulting system reduced trace-query time to about four seconds, a 50x speedup, achieved up to 89% compression, and scaled from 7 million to 400 million spans per minute in ClickHouse.
Robot policies built on vision-language-action models often struggle with physical generalization because vision-language backbones describe scenes instead of predicting physical dynamics. World action models address this limitation by building policies on video world models that jointly predict actions and future world states. NVIDIA Cosmos 3 provides an open foundation using a Mixture-of-Transformers architecture where an autoregressive transformer guides a diffusion transformer to synthesize continuous modalities including video and robot actions. Specializing Cosmos 3 on the DROID platform produced policies capable of simultaneously outputting action trajectories and predicted video observations while boosting RoboLab success from 28.1% to 36.8%. These models support flexible deployment tiers, from workstation serving on RTX PRO 6000 GPUs to real-time 15 Hz on-device execution on NVIDIA Jetson Thor embedded hardware.
Databricks announces that it is a founding member of the Open Secure AI Alliance, formed with NVIDIA and more than 75 organizations to advance openly shared AI safety, AI security, and AI-enabled cyber defense research. The alliance’s scope extends beyond model weights to an open execution stack covering runtimes, guardrails, agent harnesses, risk frameworks, and governance. Databricks contributes Omnigent, an Apache 2.0 meta-harness supporting 13+ harnesses with contextual policies, spend caps, and sandbox isolation; DASF 3.0, which maps 97 risks across 13 components to 73 controls; DAGF; and BlackIce, a containerized toolkit bundling 14 red-teaming tools. Its Lakewatch Security Lakehouse applies the same openness to governed, agentic detection and response over portable data formats.
Enterprise AI adoption across regulated industries stalls when internal governance mandates private, dedicated network paths for sensitive data. To eliminate the need for manual VPN tunnels and complex proxy layers, Salesforce re-engineered Private Connect into a multi-cloud networking platform connecting customer environments to Hyperforce services. The Private Connect v2.0 architecture utilizes private links, transit gateways, and direct endpoint routing alongside an automated control plane for rapid Hyperforce regional rollouts. In addition to supporting cross-substrate interconnects for Azure and decoupling endpoint management, the platform incorporates a generic connector framework supporting tools like Snowflake, Databricks, and Kafka. Today, the system provisions secure connectivity in under 30 minutes while processing roughly 120 TB of data and 683 million requests monthly across 15 AWS regions.
The best engineering reads, once a week.
