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
Netflix traditionally constructs its structured two-dimensional homepage through a complex, multi-stage recommender pipeline that separates candidate generation and ranking across rows and entities. To simplify this architecture and optimize directly for whole-page user satisfaction, Netflix developed GenPage, an end-to-end generative transformer model that autoregressively builds the entire homepage from raw tokenized context. The system relies on a domain-specific tokenizer to compress engagement history, context injection for cold start, hybrid row decoding to minimize decoding steps, and reinforcement learning post-training. In online A/B testing against the production baseline, GenPage delivered statistically significant gains in core user engagement metrics while cutting end-to-end serving latency by 20 percent. Offline evaluations further showed that enriching context prompts improved recommendation quality more effectively than increasing model capacity in the current operating regime.
An ETL migration with hundreds of stored procedures, schedulers, scattered permissions, and a warehouse renewal deadline needs workload-by-workload decisions rather than a single rewrite strategy. The framework assigns work among Databricks SQL, Spark Declarative Pipelines (SDP), and PySpark or Spark SQL notebooks. SQL tasks suit single statements, Unity Catalog-governed stored procedures handle procedural logic, SDP manages dependencies, retries, quality constraints, and batch-plus-streaming, while notebooks cover complex logic, ML feature engineering, integrations, and large or tightly controlled Spark workloads. It recommends four phases—assessment, quick wins, modernization, and optimization—using profiling, side-by-side validation, and parallel runs before retiring legacy systems. Migration tools can automate 60–80% of initial conversion, but architecture choices remain essential: the goal is consolidating orchestration, metadata, lineage, permissions, and validation rather than reproducing technical debt.
The NVIDIA AI-Q Blueprint operates as an open-source reference architecture for long-horizon agents built upon LangChain Deep Agents and the NVIDIA NeMo Agent Toolkit. Deploying this multi-agent system on Oracle Cloud Infrastructure requires coordinating foundational cloud infrastructure with containerized application workloads across Kubernetes. The deployment methodology utilizes Terraform to provision network isolation, an enhanced OKE cluster, a flexible public load balancer, and an AES-256 encrypted OCI Vault. Helm manages the application layer on Kubernetes by pulling official images from the NGC registry to run a FastAPI agent backend, a Next.js web frontend, and PostgreSQL. This configuration establishes an extensible routing architecture where user queries route automatically between shallow search agents and deep planning sub-agents while maintaining clean infrastructure teardown commands.
Vulkan introduces the VK_EXT_descriptor_heap extension to refactor GPU resource binding, replacing set-based layouts and pool allocations with application-managed descriptor memory heaps. This approach aligns Vulkan closer to Direct3D 12 and benefits workloads like dynamic texture indexing and complex ray tracing shaders. Developers manage memory directly, binding a single resource heap and a separate sampler heap globally to avoid high rebinding overhead. Shaders can access descriptors either through mapping structures using constant offsets or push constants, or directly via untyped pointers enabled by VK_KHR_shader_untyped_pointers. Support is integrated into NVIDIA drivers 610, Vulkan Headers 1.4.340, and Nsight Graphics 2026.2 for frame capture and inspection.
Silk is a C++ stackful-fiber library and scheduler created for ClickHouse’s highly concurrent, I/O-bound components, including object-storage I/O, distributed cache lookups, replica coordination, and HTTP fan-out. Its design combines one pinned OS scheduler thread per CPU, NUMA-aware work stealing, io_uring for asynchronous I/O and timers, and zero heap allocation in the steady-state hot path; fiber stacks are mmap’d from per-fiber pools with guard pages, while runtime containers are intrusive. The post reports benchmarks including roughly 3.6-nanosecond fiber yields with cross-CPU stealing, 5.9 million file IOPS in a working configuration, and about fifteen times boost::asio’s throughput at one connection. At 10,000 concurrent S3-style requests, internal measurements showed a roughly 65% improvement in 99.9th-percentile latency versus an equivalent thread-pool executor, with identical median throughput; distributed cache is the first intended ClickHouse integration.
Launched in 2016, MongoDB Atlas was designed to bring MongoDB's developer experience to the cloud while eliminating operational overhead for production environments. Over ten years, Atlas expanded beyond a managed database into a multi-cloud data platform that supports multi-document ACID transactions, Queryable Encryption, native search, and stream processing. The platform introduced Atlas Vector Search in 2023 and acquired Voyage AI in 2025 to embed advanced embedding and reranking models natively. These integrated capabilities address the requirements of retrieval-augmented generation and autonomous AI agents without relying on disparate vector stores or sync pipelines. Atlas now serves more than three trillion queries daily across over 125 AWS, Google Cloud, and Microsoft Azure regions for nearly 70,000 customers.
Generative AI media pipelines can exceed the memory and compute capacity of a single GPU, creating a deployment challenge for models that retain TensorRT’s kernel fusions, memory planning, and quantization. TensorRT 11.0 introduces native multi-device inference and IDistCollectiveLayer primitives, while NCCL supplies topology-aware transport across NVLink, NVSwitch, PCIe, and InfiniBand for supported distributed collectives. The article contrasts tensor parallelism, which shards layer weights, with context parallelism, which partitions sequences; it then focuses on AllGather KV, Ring Attention, and DeepSpeed Ulysses for long-sequence media attention. It also describes converting PyTorch pipelines with Torch-TensorRT into C++-deployable engines, benchmarking Cosmos 3 and FLUX.1 on an eight-GPU node, and provides C++ and OpenMPI steps for configuring an eight-rank NCCL deployment.
KRAFTON developed PUBG Ally, an on-device AI co-playable character for PUBG: BATTLEGROUNDS, using NVIDIA ACE tooling and models. Conventional non-playable characters rely on fixed dialogue, but PUBG Ally processes live game states and player voice input in real time. The interactive pipeline combines automatic speech recognition, a quantized Mistral-NeMo-Minitron-2B small language model, and a custom text-to-speech model running locally on client GPUs with at least 8GB of VRAM. To minimize latency, the architecture separates reactive gameplay into a behavior-tree System 1 layer while routing strategic decisions and speech generation to the language model. KRAFTON tuned the non-deterministic system across multi-layer evaluations and large-scale playtests with over a thousand players.
ClickHouse Cloud built WAL-RUS, an open-source Rust implementation of PostgreSQL backup and WAL archival tooling, after encountering difficulty predicting WAL-G’s memory usage in resource-constrained environments. The project preserves WAL-G’s core functionality and compatibility while using bounded worker pools, controlled concurrency, persistent object-storage connections, and a streaming pipeline that limits buffering and data copies. It uses the same WALG_ configuration variables, and WAL-G and WAL-RUS can read each other’s archives. In a sustained WAL-heavy benchmark with four archival workers, WAL-RUS stayed below 1 GB of peak virtual memory versus nearly 2.8 GB for WAL-G, while both maintained minimal backlog and comparable CPU usage. The authors plan to make WAL-RUS the default backup and archival mechanism for ClickHouse Cloud’s managed Postgres offering and are working to upstream its Postgres 17 wal summaries support to WAL-G.
Vibe.co, recently acquired by Walmart, uses ClickHouse Cloud to provide real-time campaign reporting for thousands of Connected TV advertisers across billions of ad impressions. It migrated from Postgres after aggregation-heavy OLAP queries made its pre-aggregation layer a bottleneck, limiting interactive slicing and requiring new jobs for reporting use cases. The team evaluated self-hosted ClickHouse, another managed option, and ClickHouse Cloud, choosing the latter for operational simplicity, support from ClickHouse engineers, and separation of storage and compute with more predictable costs. Vibe uses refreshable materialized views for hot/cold tiering, keeping the last 30 days in a hot table; stored data grew from about 100 GB to over 2 TB without rearchitecting, while more than 90% of client campaign reports respond in under 100ms.
Serverless PostgreSQL is presented as a fully managed cloud database model that decouples compute and storage, allowing each to scale independently with demand. Traditional deployments require teams to size infrastructure, manually manage scaling, and absorb costs from idle capacity. In serverless systems, the provider provisions compute on demand, can suspend it when idle, and bills according to active usage; scale-to-zero may introduce cold-start latency. The architecture can also support database branching through copy-on-write, creating isolated environments without duplicating data. The article distinguishes this model from lakebase architecture, which combines transactional and analytical workloads on a shared foundation using decoupled compute, durable object storage, log-based storage systems, and orchestration.
Professional basketball’s Hawk-Eye SkeleTRACK feed produces roughly 22,620 positional updates per second—about 65 million records per 48-minute game—yet teams often cannot turn that volume into timely, trusted decisions. The integration gap comes from separate vendors for tracking, wearables, video, scouting, and medical data, alongside calibration differences, weak provenance, and compute limits. The Databricks Data + AI Platform is presented as a governed lakehouse that ingests feeds with Lakeflow, refines them through medallion layers, and uses Unity Catalog for lineage, access control, and auditing. Models for shot probability, injury risk, and fatigue can run alongside serving and custom applications, with Lakebase supporting sub-second interactive queries. Applications include proactive load management, real-time coaching intelligence, and enriched broadcast or fan experiences across tracking-rich sports.
Pinterest's CDC ingestion platform relies on a multi-stage pipeline built with Kafka, Flink, Spark, and Iceberg, where upstream schema updates risk disrupting data transformations and offline storage. To prevent pipeline failures and schema drift, Pinterest introduced an automated schema evolution framework based on a staged convergence model. Upstream changes are detected via push-based DDL messages and daily pull-based validation checks. The workflow automatically restricts automated updates to additive changes and numeric precision widening, updating Iceberg table definitions and regenerating Flink and Spark code through auditable pull requests. By decoupling schema divergence, code deployment, and data convergence, the system maintains continuous ingestion availability while working toward eventual schema consistency across all storage layers.
Power costs comprise up to 40% of AI factory operating expenses, making performance per watt critical within fixed site power limits. Operators maximize throughput by combining architectural enhancements, narrow-precision formats like NVFP4, and mixture-of-experts model designs that activate fewer parameters per token. During distributed LLM training in Megatron-LM, tuning individual GPU speeds along critical execution paths eliminates idle power waste without extending total training time. Additionally, the NVIDIA DSX platform orchestrates dynamic power allocation, 45°C direct-to-chip liquid cooling, and grid integration across racks and facilities. Together, these full-stack optimizations enable performance-optimized AI factories to deliver up to 2.6 times more tokens per second per megawatt.
Transitioning autonomous agentic AI systems from sandbox environments to enterprise production exposes a trust gap driven by hallucination, reasoning errors, and financial liability. To mitigate these risks, organizations can implement a proactive four-step framework covering foundations, verification, governance, and business outcomes. The architecture grounds agents using retrieval-augmented generation, short-term memory, long-term procedural memory, and observability traces consolidated on a unified data layer. Active verification computes an Agent Confidence Score alongside a deterministic Business Risk Score to produce an Agent Decision Score governing autonomy levels. Aggregated execution telemetry feeds business observability dashboards that monitor unit economics and enable analytical agents to recommend operational interventions.
Backend security vulnerabilities often emerge from permissive default settings in web frameworks, a risk amplified when AI agents generate code focused solely on passing tests. Common failure points include unmetered request body parsing, unvalidated schemas, prototype pollution, and wildcard cross-origin resource sharing policies. To eliminate these foot-guns, the TypeScript framework DaloyJS enforces secure-by-default behavior across its entire routing and middleware model. It provides built-in request timeouts, streamed body size caps, prototype-stripping JSON revivers, and unified Zod schemas that simultaneously validate payloads and generate OpenAPI contracts. While secure defaults lower the risk of common infrastructure exploits, developers still remain responsible for application-level authorization and business logic correctness.
The article identifies ten AI business solution categories presented as growth drivers, while arguing that value is concentrated in workflows where AI changes the economics of work. It frames successful adoption around three conditions: clean, governed data; process-first use-case selection; and governance designed in from the start. Examples include customer-service agents, forecasting, personalization, intelligent process automation, and supply-chain optimization; the text says customer service accounts for 40% of top use cases, while data quality accounts for roughly 75% of what makes an AI solution work. It also describes productivity, automation, and business reimagination as distinct value paths, including a payments-data forecasting product that became an eight- to nine-figure annual revenue stream. The conclusion favors unified platforms that connect data, analytics, AI, governance, and agentic workflows.
Retrieval Augmented Generation (RAG) connects a large language model to external knowledge at inference time, addressing outdated training data and access to proprietary or real-time information. The workflow ingests and normalizes sources, splits documents into chunks, embeds them in a vector store, retrieves context, assembles a prompt, and generates an answer. Semantic search can be combined with BM25 keyword search through reciprocal rank fusion, while reranking can improve precision; the same embedding model must be used during ingestion and querying. The guide presents evaluation and deployment considerations, including separate measurement of retrieval precision and generation faithfulness, versioning, monitoring, and containerized components. It identifies poor retrieval as the most common failure mode and explains that RAG reduces, but does not eliminate, hallucinations.
The guide contrasts data lakes and cloud data warehouses for storing and querying data at scale. Data lakes retain raw structured, semi-structured, and unstructured data in low-cost object storage with schema-on-read, while warehouses enforce schema-on-write for structured analytical workloads. Lakes fit petabyte-scale machine learning, data science, and undefined future use cases; warehouses fit fast, concurrent SQL for dashboards, reporting, and operational analytics. It describes Bronze, Silver, and Gold zones, with Parquet and ORC supporting columnar scans and open-format portability. For teams combining ML and BI, lakehouses use Delta Lake, Apache Iceberg, or Apache Hudi to add ACID transactions, schema enforcement, and quality monitoring to lake storage without duplication; catalogs, staged checks, and access controls help prevent data swamps.
Telecom operators currently operate mostly within Levels 2 and 3 of the TM Forum autonomous networks taxonomy, relying on predefined scripts. Progressing to Levels 4 and 5 demands autonomous systems capable of intent comprehension, real-time telemetry sensing, and cross-domain action coordination. To address this, an autonomy platform architecture combines domain-specific reasoning models, agent harnesses, and isolated sandboxed runtimes. Workflows separate responsibilities among on-demand agents, long-running execution loops, and deep-research multi-agent systems that evaluate ranked remediation paths or design wireless algorithms. Initial experiments in simulated SR-MPLS routing and wireless physical or MAC layer design show autonomous discovery can deliver measurable gains over standard operational and engineering baselines.
The best engineering reads, once a week.
