API Versioning as a Translation Layer
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.
Loading…
Topic
Architecture
830 posts about Architecture. Every summary links to the original.
- 830 posts
- 50 companies
- 31 explainers
See the idea
Architecture explainers
BIAN as a Contract Layer: Modernizing Core Banking One Domain at a Time
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.
Argo CD: The Reconciliation Loop Between Git and Your Cluster
Argo CD is a GitOps controller that treats Git as the desired state and continuously reconciles it against what actually runs in each cluster. It maps the parts of that loop and why pull-based agents change its scale.
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
Posts
LeRobot v0.5.0: Scaling Every Dimension
LeRobot v0.5.0 is a major release that expands supported hardware, policies, datasets, simulation, and its software foundation, following more than 200 merged PRs and more than 50 new contributors since v0.4.0. It adds full Unitree G1 humanoid support for locomotion, manipulation, teleoperation, and whole-body control, alongside OpenArm, Earth Rover, CAN-bus motor controllers, and other integrations. The policy additions include Pi0-FAST's autoregressive VLAs with FAST action tokenization, Real-Time Chunking for continuously blended predictions, Wall-X, X-VLA, SARM, and PEFT fine-tuning. For data and simulation workflows, streaming video encoding removes waits between recording episodes, while EnvHub loads environments from the Hugging Face Hub and IsaacLab-Arena supplies GPU-accelerated simulation. The codebase now requires Python 3.12, uses Transformers v5, supports installable third-party policy plugins, and adds remote Rerun visualization plus installation and documentation improvements.
Designing flexible payment flows with Checkout Session
The post addresses the architectural challenge of taking a digital product business global while supporting localized tax, currencies, one-time purchases, subscriptions, and a branded embedded checkout. It recommends Checkout Sessions as the orchestration layer, with Stripe creating and managing the underlying Payment Intent while declarative parameters handle features such as Stripe Tax, Adaptive Pricing, subscriptions, and promotional codes. The implementation creates a session with ui_mode, mode, automatic_tax, adaptive_pricing, line items, and optional payment_intent_data, then passes the client secret to Stripe Elements for the Payment Element and Currency Selector. This approach supports localized payment methods and currency conversion without a backend rewrite, while direct Payment Intents remain appropriate when an application needs full control over carts, discounts, taxes, or its own checkout abstraction.
Bringing Robotics AI to Embedded Platforms: Dataset Recording, VLA Fine‑Tuning, and On‑Device Optimizations
Deploying Vision–Language–Action policies on embedded robots is constrained by compute, memory, power, and real-time control requirements; synchronous inference can leave the arm idle and cause oscillatory corrections. NXP presents dataset-recording practices for a tea-bag placement task, including fixed cameras, controlled lighting, a gripper-mounted view, calibration backups, and diverse training and validation splits with recovery episodes. The example uses 120 episodes, three 640×480 cameras at 30 fps, batch size 8, and checkpoint selection based on training and validation success rather than loss alone. For deployment, the VLA is decomposed into vision, LLM backbone, and action-expert stages, with selective quantization and asynchronous scheduling constrained by inference time being shorter than action execution. On the i.MX 95, optimized ACT latency reached 0.32 seconds with 0.89 global accuracy, while ONNX FP32 ACT reached 0.96 global accuracy at 2.86 seconds.
Introducing Modular Diffusers - Composable Building Blocks for Diffusion Pipelines
Modular Diffusers introduces a composable alternative to Diffusers’ existing DiffusionPipeline for building diffusion workflows from reusable blocks. A ModularPipeline can load a workflow definition, load model components separately with settings such as bfloat16, and preserve the familiar inference API, while blocks for text encoding, image encoding, denoising, and decoding can be inspected, run independently, or rearranged. Custom Python blocks declare components, inputs, outputs, and computation logic; the example adds a Depth Anything V2 depth processor to a Qwen Image ControlNet workflow, with data flowing between compatible blocks. Blocks and complete pipelines can be published to the Hub, and Mellon can generate node interfaces from their consistent definitions. The post presents the system as an early, flexible direction and says Mellon is not ready for production use.
Introducing ClickStack embedded in ClickHouse
ClickHouse 26.2 introduces an embedded distribution of the ClickStack observability UI packaged directly inside the ClickHouse binary. Designed for local exploration and instance inspection, this distribution allows developers to visualize internal query logs, traces, and system metrics without deploying external services. To preserve build integrity and keep the added binary footprint around 4.1 to 4.2 MB, the team avoided a Node.js dependency by embedding a pre-built static Next.js application using CMake-generated C++ structs. Supporting components such as MongoDB, Express, and the Pyodide WebAssembly runtime were omitted, disabling alerting and persistent dashboards in favor of simplicity. Users can access the interface directly over HTTP to monitor local databases and query performance out of the box.
Towards Model-based Verification of a Key-Value Storage Engine
MongoDB developers formalized the interface boundary between their distributed transactions protocol and the underlying WiredTiger key-value storage engine using a compositional TLA+ specification. This modular model established an abstract contract to verify that the storage engine's concrete timestamp-based operations matched the semantics expected by the distributed transaction layer. To check conformance, a modified version of the TLC model checker generates a complete graph of reachable states for finite parameters and computes path coverings. Each identified path is translated into an automated test case consisting of a sequence of storage engine API calls. For a finite model with two keys and two transactions, this workflow generated 87,143 test cases that executed against WiredTiger in approximately 40 minutes.
Mixture of Experts (MoEs) in Transformers
Mixture of Experts (MoEs) in Transformers let a Transformer retain its backbone while replacing selected feed-forward layers with routed expert sub-networks, allowing total model capacity to exceed the active parameters used per token. The post explains why sparse models can reduce inference cost and memory pressure, then focuses on making them first-class in Transformers. Its weight-loading refactor converts independently serialized expert tensors into packed runtime layouts through composable WeightConverter operations and lazy materialization. The Experts Backend supplies eager, batched_mm, and grouped_mm execution strategies, while expert parallelism shards experts across devices and aggregates partial outputs. Training support uses grouped GEMM and custom Triton plus LoRA kernels, with reported improvements of approximately 12× speed, over 35% VRAM reduction, and roughly 6× longer context.
Innovating with MongoDB | Customer Successes, February 2026
Modern artificial intelligence startups frequently face operational bottlenecks when deploying autonomous agents and dynamic interfaces on rigid relational schemas or restricted database engines. To address these limitations, platforms including Modelence, Thesys, Emergent Labs, and Heidi integrated MongoDB Atlas as their operational data foundation. Emergent Labs eliminated recursive schema migration failures previously encountered with PostgreSQL by adopting document structures that match native JSON generation, supporting millions of deployed applications. Meanwhile, Heidi migrated from Amazon DocumentDB to utilize MongoDB Vector Search for retrieval-augmented generation pipelines under a single unified API without requiring external search databases. These architectural transitions streamlined continuous agent iterations, eliminated operational scaling downtime, and accelerated deployment cycles across diverse production environments.
We proactively fixed ~100 security issues in 6 days with 0 humans
Ramp Security Engineering describes a six-day experiment in which home-grown agents found, validated, and fixed nearly 100 latent backend security issues, including some high-severity findings, without human involvement until pull-request review. The issues had not been uncovered by penetration testing, bug bounty testing, static analysis, or trials of 10+ code-scanning vendors, and all were patched within a week of discovery. The pipeline used specialized vulnerability detectors, adversarial manager agents that rejected 40% of initial proposals in sample testing, integration tests for validation, and an internal coding agent that generated patches. Live interactive validation struggled with complex preconditions, so test-based validation became the main approach; a human team member still reviewed and landed each pull request.
Scaling Localization with AI at Lyft
Lyft re-architected its batch localization pipeline to combine artificial intelligence with professional linguist oversight. The previous workflow relied exclusively on human translation, which resulted in multi-day turnarounds and linear cost scaling that hindered rapid market expansions. Under the new architecture, a dual-path system generates three candidate translations using a fast generation model, evaluates them against defined rubrics using a reasoning-focused model, and immediately releases approved drafts. Linguists review the drafts asynchronously in the Smartling translation management system to establish the final system of record. This pipeline reduced delivery latency from days to minutes while achieving a state where 95% of machine-generated translations require no significant changes during human review.
Building a mental model for Stripe payments
An online bookshop checkout must coordinate card networks, issuing banks, fraud checks, regulatory requirements, currencies, and varied payment methods while completing in roughly 2–3 seconds. Stripe abstracts these concerns through a unified API, with the PaymentIntent representing the payment lifecycle from amount and currency collection through tokenization, authorization, capture, and settlement. The Payment Element and client-side tokenization keep sensitive card details away from the shop’s servers, while Stripe may perform risk checks and additional 3D Secure authentication. Because payments can change state minutes, hours, or days later through refunds and disputes, webhook events should be treated as the source of truth for synchronizing order and downstream systems without polling.
Minions: Stripe’s one-shot, end-to-end coding agents—Part 2
Stripe’s minions are an unattended agentic coding flow whose pull requests are human-reviewed but contain no human-written code; more than 1,300 merge weekly. The system runs agents in AWS EC2-based devboxes that are prewarmed to become usable within about 10 seconds, providing parallel, predictable, and isolated environments. Its custom harness uses code-defined blueprints that combine deterministic nodes, such as linting and pushing changes, with agent loops for tasks such as implementation and fixing CI failures. Minions receive automated feedback through local linting, one full CI iteration, and a possible second repair attempt, while devbox isolation and security controls limit destructive actions; Stripe presents the approach as an extension of long-running investments in human developer productivity.
Custom Kernels for All from Codex and Claude
Writing CUDA kernels that integrate with diffusers and transformers involves GPU-specific optimization, library integration, PyTorch registration, and environment compatibility. It presents a cuda-kernels agent skill that packages architecture guides, integration patterns, kernel templates, troubleshooting material, benchmarks, and Kernel Hub examples for coding agents. Claude and Codex used it to generate RMSNorm, RoPE 3D, GEGLU, and AdaLN kernels for LTX-Video in diffusers, and an RMSNorm kernel for Qwen3-8B in transformers, including CUDA source, PyTorch bindings, build configuration, and benchmark scripts. On H100 80GB HBM3, the LTX-Video RMSNorm tests averaged 1.88x speedup and the optimized pipeline with torch.compile reached 1.43x the listed baseline, while Qwen3-8B RMSNorm averaged 1.94x and reached 2.47x at 8192 tokens. The skill supports packaging kernels for precompiled distribution through the Hub, where get_kernel selects a matching binary across Python, PyTorch, and CUDA variants.
Transformers.js v4: Now Available on NPM!
Transformers.js v4 is now available on NPM, marking a major release after a year of development. It introduces a C++-rewritten WebGPU runtime tested across about 200 supported model architectures, enabling the same JavaScript code to run WebGPU-accelerated models in browsers, Node, Bun, Deno, and desktop applications. Specialized ONNX Runtime Contrib Operators support new export strategies for large language models, and the post reports a roughly fourfold speedup for BERT-based embedding models using MultiHeadAttention. The release also restructures the repository as a pnpm-workspaces monorepo, modularizes model definitions, moves examples to a separate repository, and switches from Webpack to esbuild, reducing build times from two seconds to 200 milliseconds and shrinking transformers.web.js by 53%. New APIs cover model asset inspection, caching, environment fetch controls, logging, and standalone tokenization, while added architectures include Mamba, MLA, and MoE models compatible with WebGPU.
Towards self-driving codebases
The post describes research into scaling long-running autonomous coding agents, using a web browser as a complex benchmark and running thousands of agents continuously for one week. An initial single-agent plan failed because the model lost track, stopped prematurely, and stalled on complex details; shared-state coordination then introduced locking contention, while more structured planner, executor, worker, and judge roles improved ownership and throughput. The team built a Rust-based harness on one large Linux VM, logged agent messages and tool activity for replay and analysis, and iterated through designs that eventually favored a more dynamic system with freshness mechanisms and fewer overloaded roles. The research concludes that architecture, prompts, observability, explicit throughput trade-offs, and anti-fragile recovery matter, reporting linear scaling of token throughput with minimal harness overhead while humans retained taste, judgment, and direction.
Edge AI Made Easy: MongoDB and ObjectBox Data Synchronization
Modern edge AI deployments require immediate real-time decision-making, local privacy, and offline operation while retaining the analytical scale of central cloud infrastructure. To address these hybrid demands, MongoDB and ObjectBox partnered to release the ObjectBox MongoDB Sync Connector as part of ObjectBox 5.0. ObjectBox operates as a lightweight on-device database with local vector search, multi-language bindings, and high-throughput I/O suited for resource-constrained hardware. In environments such as industrial factory floors and restaurant point-of-sale terminals, devices capture and evaluate operational data onsite without depending on active network connections. The native connector subsequently synchronizes critical operational datasets to MongoDB Atlas for long-term storage, fleet-wide monitoring, and machine learning model retraining.
The Future of the Global Open-Source AI Ecosystem: From DeepSeek to AI+
This third and final article in a series examines how Chinese AI organizations are shaping an open-source ecosystem after DeepSeek R1's January 2025 release. It argues that open sharing of models, papers, deployment infrastructure, and techniques has become the dominant near-term approach, with organizations ranging from Alibaba, Tencent, ByteDance, and Baidu to startups and application companies contributing at different layers. Qwen illustrates the ecosystem strategy: by mid-2025, more than 113,000 Hugging Face models used Qwen as a base, while organizations also connected models with chips, cloud platforms, toolchains, evaluation, and deployment systems. The article places this shift on infrastructure built since 2017, including the East Data, West Compute plan, and says R1 catalyzed wider use of existing compute, energy, and data capacity. It concludes that open-source models are becoming reusable, composable components in industrial workflows and localized AI systems as China moves from DeepSeek toward AI+.
Architectural Choices in China's Open-Source AI Ecosystem: Building Beyond DeepSeek
Chinese open-source artificial intelligence development has shifted focus toward architectural choices, ecosystem toolchains, and domestic hardware integration following the January 2025 DeepSeek release. Leading groups have adopted Mixture-of-Experts architectures like Kimi K2 and Qwen3 to balance capability, dynamic compute allocation, and operating costs. Development expanded beyond text into multimodal domains including speech, video, and 3D systems while prioritizing smaller 0.5B to 30B distilled models under permissive Apache 2.0 licensing. Furthermore, model releases increasingly provide day-zero alignment with domestic inference and training infrastructure, including Huawei Ascend, Cambricon, and Baidu Kunlun chips. Production serving engines such as Moonshot AI's Mooncake and Baidu's FastDeploy 2.0 reflect a transition from standalone models to comprehensive system-level design.
Configuring Stripe using Terraform and AI agents
The post addresses the difficulty of using AI agents to configure Stripe resources when one-off API calls leave no durable source of truth for state, changes, or environment differences. It recommends using agents to author Terraform configuration rather than operating Stripe directly, so products, prices, and webhook endpoints become explicit, reviewable code. The example defines a Standard Plan with $20 monthly and $200 annual prices, selected webhook events, and outputs for both price IDs, then applies it with terraform plan and terraform apply. Terraform provides declarative, repeatable configuration supported by Git history, pull-request review, and environment-specific workspaces. Separate sandbox and livemode workspaces, paired with matching STRIPE_API_KEY values, are presented as a way to reduce accidental cross-environment changes.
First Block with Gerry Giacomán Colyer, Co-founder and CEO of Clara
First Block features Gerry Giacomán Colyer, Clara’s co-founder and CEO, discussing the company’s founding, rapid growth, and expansion of AI agents for finance operations across Latin America. Clara’s bank partner shut down only months after launch, prompting the team to secure direct issuer licenses with Visa and MasterCard in two weeks and build more robust infrastructure from the outset. The episode connects that resilience to product-led growth: a self-serve onboarding flow supported more than 20,000 customers across three countries, from pre-revenue startups to the Mexican Stock Exchange. The company is now applying its transaction data across Latin American businesses to a financial analyst agent that automates policy enforcement and approval workflows. It also covers the founding lesson from a previous company’s financial-tooling difficulties, early milestones, scaling decisions, and a roadmap across markets, alongside questions about efficiency, resilient infrastructure, and distinctive data advantages.
Related topics
All topics →Weekly digest
The best engineering reads, once a week.