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
Canva’s queue workers were designed to consume messages greedily, but that behavior could amplify dependency failures, waste scarce capacity, fill dead-letter queues, and create on-call work. Worker Backpressure adds a local feedback loop to the shared queue library: each processed message reports success or failure, a pluggable controller maintains a 0.0-to-1.0 backoff factor against a configured failure-rate set point, and permits scale concurrency at each poll. The mechanism requires no external coordinator or network calls and adds two arithmetic operations to the runtime path, while trading some throughput for failure containment. In two production incidents, it reduced worker pressure during errors and recovered automatically; one sustained-overload incident recorded a 2.76% average failure rate, 22 DLQ messages over 32.5 hours, and no paging, while rollout to all queue workers remained the immediate goal.
Outdated architecture diagrams and static code analysis can miss how services are connected at runtime, so the OpenTelemetry plugin builds a Service Map from live telemetry. With a lightweight local OpenTelemetry backend, the plugin supplies standard OTel environment variables, receives application spans, and continuously updates an internal architecture model that the IDE renders on demand. Its stream-processing algorithm classifies spans through semantic attributes, identifies services, matches HTTP CLIENT and SERVER spans across propagated trace context, and infers database or messaging dependencies while retaining unmatched spans in memory. Because spans can arrive out of order and traces have no definitive finish signal, the map is incrementally reconstructed rather than built from complete traces; the result is a language- and vendor-agnostic view for OpenTelemetry-instrumented applications across several JetBrains IDEs.
Many retail loyalty programs use batch processing, delaying rewards by up to 72 hours or 10 business days, eroding customer trust. Nearly 75% of shoppers prefer instant rewards, 82% of Gen Z and Millennials expect real-time responsiveness, and real-time credit can increase basket size by 36% and spending by 2.5 times. Relational databases struggle with atomic writes across multiple tables, forcing batch cycles; layering microservices on top only distributes fragmented data without solving latency. MongoDB’s document model solves this by storing the complete loyalty profile in a single document for atomic writes; Triggers and Change Streams push updated balances instantly and allow promotional rule changes without redeployment. This architecture turns the post-purchase moment into immediate reinforcement, reduces support inquiries, and drives engagement, as seen with Starbucks Rewards contributing nearly 60% of total revenue.
Agentic LLM systems that generate code through multi-turn tool use lose configuration choices, domain constraints, schemas, and tool-use patterns when each session starts from zero. The proposed shared selective persistent memory retains task specifications, data schemas, tool configurations, and output constraints while discarding session-specific reasoning traces, and allows workspaces to be transferred across users with role-based access control. In a deployed collaborative workspace platform, agents create and maintain git-versioned dashboards, reports, and data-driven documents from CSV, SQL, REST API, and MCP sources; draft isolation supports risk-free changes and restoration without re-invoking the model. Results across three enterprise scenarios show 96% task completion, compared with 79% without memory and 71% with full history, while zero-token refresh cut recurring-update task time 14× and summary-driven generation reduced token cost 97× versus raw data injection.
Dense models activate every parameter for every token, while Mixture-of-Experts (MoE) models route each token through a selected subset of feed-forward experts. This changes the relationship between capacity, memory, and compute: total parameters determine the memory required to load a model, whereas active parameters largely determine per-token work. At equal total size, MoE models often provide higher throughput, especially at batch size one, but routing, simultaneous expert residency, and reduced KV-cache room add serving complexity; latency advantages narrow at high concurrency. The comparison uses Nemotron 3.5 Lightning, a roughly 30B-parameter Mamba-2 plus MoE plus Attention hybrid with 3B active parameters, alongside dense and MoE examples, and concludes that dense models suit simpler serving and fine-tuning while MoE models suit throughput-oriented deployments with manageable memory and operational complexity.
NVIDIA NVLink 6 is presented as a scale-up networking fabric for large AI factories, where dropped packets, link degradation, and node interruptions can reduce training goodput or inference capacity. It connects 72 Rubin GPUs in the Vera Rubin NVL72 into a single scale-up domain and uses a multi-layer resiliency stack spanning physical, link, application, software, and system layers. Physical Layer techniques include lightweight FEC, Physical Layer Retry (PLR), UPHY recovery, and hardware replay buffers, while credit-based flow control (CBFC) prevents injection when the next hop lacks buffer capacity. Redundant switch trays and management paths, local fault containment, NMX high availability, checkpointing, topology-aware recovery, and targeted switch maintenance are described as mechanisms for containing failures and preserving workloads; the post concludes that this integrated design targets continuous operation and maximum cluster productivity.
AI coding agents can generate services quickly, but they may miss organization-specific architecture, ownership, and compliance rules stored in an internal developer portal. A demo connects Claude Code to a Backstage-based Red Hat Developer Hub through Backstage CLI actions, allowing the agent to query domains, components, APIs, software templates, and TechDocs before proposing a design. In a simulated Parasol Insurance catalog with more than 500 entities across 14 domains, the agent finds an existing but unrelated reconciliation service and resolves a Claims–Billing messaging conflict by keeping IBM MQ at the payment boundary and publishing internal events to Kafka. It then uses catalog relationships and specifications to identify integrations and produces a Technology Decision Summary that cites the sources behind each choice, making the resulting decisions reviewable and traceable.
Salesforce’s AI Engineering team uses Data 360 data graphs to close the context gap that prevents agents from reliably personalizing customer interactions. The graphs join, aggregate, and apply business logic across fragmented identities, accounts, products, contracts, orders, cases, services, and entitlements, while partitioned data spaces provide a filtered customer-success view. The team designs smaller graphs or multi-graphs around agent access patterns, adds indices, supports semantic or keyword search, and curates context so agents can traverse extensible many-to-many relationships without receiving unnecessary data. Reusable deployment automation and validation practices helped deliver five major releases in six months, with integrations spanning Postman, Apex, Agentforce, and low-code or no-code workflows. Live monitoring later showed P50 performance below 200 milliseconds, compared with an earlier benchmark of about 400 milliseconds.
SimpleDesign addresses protein design as a joint modeling problem involving amino acid sequences and three-dimensional structures, whose interplay determines protein function. Unlike approaches that first train autoencoders and then model their latent representations, it uses a single-stage, end-to-end objective directly in data space. The objective combines discrete cross-entropy for sequences with a regression objective for structures, while Transformer-based multimodal backbones provide modality-specific processing and global self-attention across both modalities. Trained on more than 2M sequence-structure pairs, SimpleDesign achieves competitive performance on co-design and unconditional sequence and structure generation benchmarks. The work argues, based on these results, that multi-stage training is not necessary for performant co-design models.
Anthropic announced that Rahul Patil has joined as its Chief Technology Officer, overseeing engineering across product, compute, infrastructure, inference, data science, and security as Claude scales to meet growing enterprise demand worldwide. Patil brings more than 20 years of experience building and maintaining industry-leading infrastructure, most recently as CTO of Stripe, where he guided technology supporting millions of businesses processing more than trillion dollars annually. Earlier roles at AWS, Microsoft, and Oracle Cloud Infrastructure developed his expertise in reliable, scalable mission-critical systems, while co-founder Sam McCandlish moves from CTO to Chief Architect to focus on large-scale model training, pretraining, research productivity, and RL infrastructure. The announcement frames Patil’s appointment as a commitment to world-class infrastructure and reliability at scale for developers building with Claude.
JetBrains IDEs have supported WSL through several architectures, but the 2026.2 release makes Native mode the recommended entry point for projects stored there. In Native mode, the Windows IDE delegates filesystem and process operations to the Rust-based IJent agent inside WSL, with EelApi abstracting local and remote environments for IDE and plugin code. Earlier approaches included 9P filesystem access, WSLg, and Remote Development, with problems involving symlink handling, latency, GUI limitations, installation overhead, and client–backend communication costs. Performance tests on a cold first open of spring-framework measured Native mode at 11.5 seconds to become ready versus 18.5 seconds for 9P, while project-tree scanning took 3.7 versus 8.1 seconds. Remote Development remains available, but direct project opening is now preferred in IntelliJ IDEA, WebStorm, and PhpStorm.
Salesforce Health Insights addresses enterprise org health monitoring by combining configuration metadata with runtime telemetry to identify and prioritize remediation. The team evolved a static report into an in-app experience with durable finding dispositions, approximately 400+ signals across domains, and standards informed by Well-Architected principles and implementation anti-patterns. A shared harmonization layer reconciles fragmented datasets, connector patterns link runtime activity to metadata components, and the system preserves data origin, freshness, and access requirements while keeping deterministic findings distinct from externally supplied context. Prioritization combines findings with request volume, application and database CPU, call behavior, and peak-business-hour traffic to rank next best actions by criticality and effort. A headless JSON schema supports interfaces including an MCP connection, while the deterministic core is intended to produce dependable recommendations and extend access beyond the primary interface.
Ceilometer is Uber’s adaptive benchmarking framework for qualifying new server types, cloud SKUs, kernel upgrades, configuration changes, and machine-learning frameworks before production rollout. It replaces manual, fragmented testing with standardized configurations, automated cluster bring-up and service deployment, portable containerized harnesses, and reporting that includes server specifications, reference SLAs, normalization, resource utilization, cost efficiency, and reliability signals. Its distributed architecture runs synthetic and production-like workloads across dedicated machines, processes and enriches raw results, stores them in blob storage and a centralized data warehouse, and exposes them through an analytics service. The framework covers CPU and memory benchmarks, tools such as SpecCPU2017, SPECjbb2015, NetPerf, and FIO, plus stateful, stateless, batch, and ML workloads; Uber reports uses including regression detection, database validation, and canary testing of external upgrades.
The workflow replaces a manual, fragmented process for turning a simple ServiceNow connectivity request into firewall changes. Event-Driven Ansible connects ServiceNow, GitHub, an LLM, and two Palo Alto Networks firewalls, checking drift, gathering topology data, and coordinating structured rule proposals, pull requests, and workflow records. Ansible Automation Platform keeps credentials away from the AI and deploys approved rules through a deterministic, idempotent path after engineer and CAB approvals. GitHub’s main branch records the last successful state, proposed changes are reviewed as Configuration as Code, and execution stops when live configuration differs from the intended state. The lab demonstrates partial coverage, no coverage, and an unresolvable request; failed deployments can roll back, while an undefined Palo Alto Networks App-ID stops the workflow for human intervention.
Agentforce faced a production problem: LLM-driven rendering could recognize a required form or regulated disclosure yet choose a different output because its reasoning was stochastic. The Agentforce Connections layer addresses this by separating probabilistic reasoning and orchestration from deterministic presentation: builders associate an action with a connection-specific response format through the render: directive, and the platform applies that format instead of asking the LLM to select a component. Multi-action, long-running, and supervised flows required the system to identify the configured action and render only after approval and execution. The same abstraction supports Lightning Web Components, third-party interfaces, and headless structured JSON outputs. Per-action, per-session event logs record the action, format, connection, and conversation point, providing auditable evidence that required rendering occurred.
ZGateway is a stateless proxy tier introduced to unify traffic from ZippyDB’s large, diverse client fleet and address the reliability limits of direct access. By terminating TLS, authorizing requests, applying admission control and shaping, and routing through regional tiers, it replaces a many-to-many connection mesh with bounded client-to-gateway and gateway-to-server hops. Its embedded thick C++ client batches and coalesces shard requests, while a shared pipeline supports pure-proxy and read-through-cache tiers; per-use-case metrics, traces, and quota usage provide operational visibility. The gateway handles more than 1 billion operations per second, carries about 40% of ZippyDB traffic, and adds about 6% computational overhead to an average use case, with traffic projected to exceed 60%; production work also consolidated transaction state handling across 100% of transaction traffic without a reliability regression.
Organizations often retain specialist knowledge in experts’ heads, leaving routine compliance assessments slow, inconsistent, and difficult to scale. The proposed “second brain” combines a structured, auditable knowledge architecture with a separate reasoning layer and a self-improvement loop that converts expert feedback into verified, regression-tested text updates without model retraining. High-density organizational positions, taxonomies, routing indexes, and gateway files are maintained in a dependency-linked filesystem, while sparse supporting material remains available through semantic or lexical retrieval. Composable recipes encode expert procedures, and an evaluation pipeline proposes auditable pull requests, retries failed fixes, and expands regression coverage after approval. After six weeks, SMEs reportedly found outputs useful almost always, assessments fell from days to minutes, and improvement cycles produced zero regressions; the architecture is presented as applicable beyond compliance.
REFACTOR-VLA addresses the weakness of monolithic vision-language-action (VLA) models, which generate raw commands or short action sequences and struggle with long-horizon tasks and interpretability. Its wake/sleep architecture uses a Behavioral-Equivalence Kernel (BEK) to cluster motor-program segments by outcomes from a learned latent world model, then produces typed lambda terms for a library-conditioned rectified-flow action decoder. Skills are admitted only when they satisfy both Minimum Description Length (MDL) and return-preservation gates, while training proceeds through world-model warmup, wake-phase policy optimization, and sleep-phase skill discovery. On the full LIBERO benchmark, expanding the world model from 188 million to 430 million parameters worsened results on all four suites, showing that scale alone was not beneficial. Adding supervised contrastive InfoNCE loss during warmup substantially improved sleep-phase clustering, with reported NMI scores of 0.462, 0.867, 0.915, and 0.754 for the Object, Spatial, Goal, and LIBERO-10 suites, respectively, under n = 3 multi-seeding.
Shared-nothing architecture is presented as a scaling model for Showcase, a Ruby on Rails ballroom-competition application that began on a Mac Mini and grew to cloud VMs serving events in multiple regions. Because each event has few geographically concentrated users, a roughly one-megabyte SQLite database, about one transaction per second, and typical response times of 100ms or less, the design keeps state separate rather than sharing databases and Redis across events. The implementation runs an event’s services on one Fly.io VM, repeats that unit across machines or regions, and can place multiple event instances on one server with Phusion Passenger, NGINX, volumes, and a shared Action Cable process. It specifies 1GB machines with 2G swap after observing about 220MB idle and 450MB active RAM, and recommends WireGuard; the conclusion is that local state and fewer network calls suit this workload and can improve throughput and reliability.
The Databricks Partner Network has launched Bronze, Silver, Gold, and Platinum tiers for ISVs and data providers, with placement based on customer impact, technical excellence, strategic alignment, readiness and enablement, and joint go-to-market activity. Technical Excellence is evaluated through the Partner Well-Architected Framework (PWAF), which provides prescriptive, AI-ready guidance for secure, reliable integrations and serves as the standard for validated architecture. For customers, the tiers signal that a partner solution has met a high bar for architecture, security, compliance, and joint customer success, reducing vetting effort. For partners, each tier defines requirements and a roadmap tied to greater visibility, co-selling, and go-to-market support, while Databricks plans to refine the program and expand benefits over the coming months.
The best engineering reads, once a week.
