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
Bosch Mobility Platform Solutions developed the Logistics Operating System on AWS to unify vehicle tracking across fragmented spot logistics markets. The system standardizes multiple telematics providers, disparate data formats, and diverse communication protocols into a centralized visibility layer. Orchestration is handled by a Tracking Connector running on Amazon ECS with AWS Fargate, while AWS Lambda functions act as provider-specific adapters for protocol translation. Event-driven message ingestion and streaming rely on Amazon MSK, complemented by Amazon ElastiCache for low-latency caching and Amazon DynamoDB for compliance policy enforcement. Currently operational in India with ten integrated ISVs, the platform reportedly reduces integration costs by 15–20% and lowers total tracking costs for small transporters by 25–30%.
Scottish Water’s Capital Investment teams had project data, reports, and metrics available, but non-technical users often struggled to find answers, creating duplicated reporting and delays. SPARK addresses this access problem through a natural-language interface in Microsoft Teams: Copilot routes questions via a supervisor agent and MCP to the Databricks Genie Agent, which queries governed Unity Catalog data. The implementation curates use-case data in a gold layer, adds metric views as a semantic layer, and configures business rules, examples, benchmarking, feedback, and monitoring for accuracy and performance. Environment-parameterised Databricks Asset Bundles, separate environments, Azure DevOps approvals, Entra ID, and Key Vault support repeatable deployment. The post reports lookup journeys shrinking from around eight clicks or four to five search steps to a direct question, with an estimated 520 to 1,300 hours saved annually under a stated usage scenario.
When multiple departments share a single foundation model in Amazon Bedrock under one IAM role, usage aggregates into one billing line item, complicating department-level chargebacks and budget tracking. This issue can be resolved by deploying Amazon Bedrock application inference profiles wrapped around the shared foundation model and tagging each profile for cost allocation. The application layer determines the user department during authentication and passes the corresponding inference profile ARN as the model identifier. Once the designated cost allocation tag is activated in the AWS Billing and Cost Management console, usage separates into per-department line items in AWS Cost Explorer. This method incurs standard per-token model rates without extra charges for cost attribution.
Organizations operating under data residency requirements must balance jurisdictional compliance with disaster recovery objectives for critical workloads on AWS. In locations served by a single Region or facing multi-Region constraints, three architectural patterns offer distinct trade-offs between regulatory adherence and operational complexity. The cryptographic boundary approach replicates encrypted data to another AWS Region while restricting decryption access using AWS Key Management Service policies. The data boundary pattern deploys AWS Outposts on-premises within the source country while relying on an external parent Region control plane. Finally, strict local autonomy boundaries retain data and control planes entirely in-country through on-premises systems or multi-cloud lifeboats, requiring rigorous end-to-end continuous testing.
Cloudflare announced the general availability of Certificate Transparency Monitoring alongside a filtering mechanism to eliminate noisy alert emails. Previously, the monitoring system alerted domain owners for all Certificate Transparency log entries, including routine, automated renewals for Universal SSL, Advanced Certificate Manager, and backup certificates. Because the alerting flow and certificate ordering service operated independently, existing identifiers like TBSCertificate hashes arrived too late to verify pre-certificates. To resolve this race condition, the ordering service now computes an SHA-256 hash of the DER-encoded SubjectPublicKeyInfo structure at key generation. When the alerting service discovers a log entry, it recomputes this hash to verify ownership against the ordering database, suppressing alerts for Cloudflare-managed certificates while preserving alerts for external or unexpected issuances.
In Text2SQL systems, generating SQL on the fly with frontier foundation models can cause response times of 25 to 30 seconds due to 60,000-token prompts and model latency. To solve this without degrading accuracy, an intelligent caching layer was built using parameterized SQL query templates paired with question embeddings. When an incoming question matches a cached template via semantic search above a confidence threshold, named entity recognition extracts values to populate template placeholders, bypassing the initial SQL generation step. In production, this approach reached a 60% cache hit rate after two weeks, cutting per-hit token consumption by roughly 90% and reducing overall latency by 80% to under 5 seconds.
Databricks’ serverless platform launches tens of millions of VMs daily, and each VM needs network configuration before serving customer workloads. The original design synchronously aggregated data from multiple upstream services on the cluster-creation critical path, producing 5,000-ms p99 RPC latency and availability bottlenecks as request volume reached billions per day. The replacement uses change events through a message queue, asynchronous per-workspace recomputation, partition-local snapshots, and periodic reconciliation to recover from missed events. The serving path now performs a single snapshot-store read without upstream calls, while events carry workspace and resource identifiers rather than customer data. After rollout, p99 RPC latency fell to 125 ms, server success rate rose to 99.99%, upstream call volume dropped 86%, and the legacy synchronous framework was deprecated.
Salesforce engineers expanded Security Center from a basic conversational interface into an Agentforce-powered stateful investigations platform for incident response. Managing enterprise security incidents required handling long-running lifecycles, disparate telemetry formats, and finite LLM context windows that risk reasoning pocket collapse. To prevent overflowing context limits, the architecture partitions telemetry into contextual segments and uses AI-driven summarization pipelines before feeding data to the agent. Because non-deterministic LLM outputs break traditional deterministic testing, the team implemented AI-driven evaluation pipelines using simulated customer interactions to evaluate response behavior rather than exact wording. Ongoing work focuses on grounding public foundation models with curated, Salesforce-owned security knowledge to improve platform-specific remediation guidance.
Alibaba’s Qwen3.8-2.4T-A95B (Qwen3.8-Max) is an open-weight 2.4T-parameter model with 95B activated per token, designed for reasoning and agentic workloads. Its fine-grained mixture-of-experts architecture combines full and linear attention, supporting context of up to one million tokens and output lengths up to 128K while using bounded recurrent state in linear-attention layers. NVIDIA describes multinode serving on the 72-GPU GB300 NVL72, where a 130 TB/s NVLink domain supports expert communication; in FP8, the model reportedly exceeds 4K tokens per second per GPU and 350 tokens per second per user without additional tuning. Developers can control reasoning depth with low, high, or xhigh modes, choose SGLang, vLLM, NVIDIA Dynamo, or NIM for serving, and use NeMo AutoModel for full SFT or LoRA post-training.
Airbnb overhauled its login and registration architecture by transitioning to a server-driven framework called Flexible Authentication. The new system separates user identification from verification, using a backend policy engine to dynamically serve the optimal auth challenge and fallback options based on regional and user context. This shift eliminated dead ends, reduced client bundle sizes, and dramatically sped up experimentation velocity across Web, iOS, and Android.
AI infrastructure spans compute, networking, storage, orchestration, and applications, so a symptom at one layer may originate elsewhere. The post proposes selecting observability tools by failure domain, mapping components to telemetry sources, and reducing signals to a top-k alert set in a unified Prometheus/Grafana triage dashboard. For a DGX cluster using InfiniBand, BCM, and Slurm, it recommends Redfish/IPMI, DCGM, NVSM, UFM, and BCM, while deferring NetQ, NMX, Run:ai, and NIM until their corresponding capabilities are needed. The framework emphasizes DCGM for GPU metrics, NVSM for DGX system health, UFM for InfiniBand, and BCM for cluster and job aggregation, with specialized tools retaining low-level telemetry. An elevated InfiniBand bit error rate illustrates how retransmissions can slow one rank during NCCL all-reduce, causing synchronized training throughput to follow the slowest rank; alerts should connect concise signals to owners and remediation actions.
Traditional multi-agent architectures rely on a central supervisor agent to decompose tasks and aggregate results, creating single points of failure and context-window throughput bottlenecks. To address these scaling limits on decomposable workloads, kiro-flock implements self-organizing clusters of headless Kiro CLI agents on Amazon EC2 coordinated entirely through shared Amazon S3 state. Agents operate in bounded peer topologies such as logical rings, reading neighbor append-only logs and generating artifacts without direct inter-agent messaging or central brokers. Each agent starts fresh per iteration without conversational memory, reading current direction and peer logs to prevent drift and preserve steering control. This shared-state pattern enables resilient parallelism for tasks requiring diverse independent contributions, such as code reviews or codebase migrations.
JetPack 7.2.1 adds support for PyNvVideoCodec 2.2, NVIDIA's Python library for hardware-accelerated video encoding and decoding on GPUs, alongside foundational agentic video skills for Jetson workflows. These skills inspect the live target, query codec capabilities, generate Video Codec SDK or PyNvVideoCodec recipes, execute runs, and return measurements, warnings, and reproducible evidence. PyNvVideoCodec keeps frames in GPU-resident device memory through DLPack and CUDA device buffers, with multi-mode frame sampling and a ThreadedDecoder that pre-decodes frames in a background thread. The release also enables emulation of recently announced Jetson T3000 performance on a Jetson T5000 module in the Jetson Thor AGX Developer Kit, while the video skills are limited to Video Codec SDK and PyNvVideoCodec stages.
NVIDIA NeMo Switchyard addresses the problem of routing AI-agent work across models with different capabilities, costs, latency, and verbosity profiles rather than sending every request to one model. At runtime, its router evaluates a request, context, policies, and system signals, then directs work to a configured model pool, potentially routing individual agent steps and carrying session state when needed. The provider-agnostic switchyard-libsy SDK separates semantic model targets from provider endpoints, while a reference server accepts OpenAI, Anthropic, and Responses API requests and records routing decisions and outcomes. Available approaches include tuning-free LLM classifier, stage, and escalation routers, alongside tunable and custom algorithms. In a LangChain evaluation, escalation routing cut cost 74% versus a frontier-only baseline with a measured six-point accuracy trade-off, while Cognition’s staged routing reported near-frontier coding performance at approximately 28% lower mean cost.
In the first half of 2026, network-layer DDoS attacks exceeding 1 Tbps surged by 519% quarter-over-quarter, with 935 mitigated attacks recorded across the period. Threat actors shifted their focus toward reflection and amplification methods, making DNS-based floods and CLDAP floods the dominant vectors. Despite the rise in hyper-volumetric traffic, 96.62% of network-layer attacks remained under 500 Mbps and 90.60% ended in under 10 minutes. Geopolitical conflicts and international events heavily influenced target selection, pushing the Media, Production & Publishing industry to the top position. Because brief multi-gigabit bursts trigger downstream routing instability and application timeouts before analysts can respond, automated, always-on edge mitigation has become critical.
The piece argues that modern risk failures stem less from modeling weakness than from slow, fragmented data architecture. It uses Silicon Valley Bank, Archegos, and the UK LDI crisis to show how batch processing, siloed counterparty data, and static stress tests can obscure liquidity, aggregate exposure, and feedback loops until intervention is difficult. Its proposed shift is a unified Databricks Data and AI Platform combining governed data, real-time aggregation, lineage, scenario analysis, and AI-assisted investigation across risk functions. Specific capabilities described include Unity Catalog permissions and lineage, VaR or Expected Shortfall deltas computed in seconds, and SQL-auditable natural-language queries with MLflow-backed model provenance. The conclusion is that real-time, defensible risk visibility supports the CRO’s expanding role in capital allocation and growth, with Raiffeisen Bank International, Morgan Stanley, and State Street cited as production examples.
Databricks says Electric is joining the company to extend its Postgres capabilities from the lakehouse to AI agent sandboxes. The post frames agentic applications as requiring both durable governed state and rapidly changing local context: agents choose data at runtime, operate in sandboxed environments where cloud databases are reached over the network, and collaborate while working in parallel. Electric’s PGlite is a lightweight Postgres database built for WebAssembly that runs inside an agent, application, browser tab, or device, while its real-time sync engine synchronizes distributed data with centralized Lakebase infrastructure. PGlite’s weekly downloads reportedly grew from 1 million to 13 million in twelve months, and the sync architecture is described as keeping agents’ shared context current. Combined, Lakebase, PGlite, and synchronization are presented as a Postgres-based foundation for collaborative agentic applications at production scale.
Salesforce faced scaling bottlenecks when individual engineering teams maintained fragmented, custom telemetry pipelines requiring manual data transformations and dashboard creation every release. To resolve these silos, the engineering organization established the Product Data Platform (PDP) using a standardized custom schema built atop Monitoring Cloud infrastructure. This framework mandates core telemetry fields for consistent metric generation while offering governed optional attributes for product-specific flexibility. An AI-driven Model Context Protocol tool assists developers by recommending compliant instrumentation patterns directly within their workflows. Today, the unified platform processes 45 billion rows of data daily across 19,000 distinct events and 2,000 product features, reducing dashboard refresh latency by 97 percent from one month to daily updates.
Databricks Genie Agents can combine structured tables and unstructured documents, but the central challenge is preserving data governance when one agent can access both. The proposed architecture runs agents with the end user’s credentials, using Unity Catalog identity synchronization, object privileges, ABAC policies, row filters, and column masks to enforce permissions at query time. Automatic Identity Management syncs users and groups from Microsoft Entra ID and Okta, while just-in-time provisioning carries current memberships into Databricks. Structured assets include tables and metric views, and governed tags can attach protection across newly tagged data; documents are governed through Unity Catalog volumes and their grants. In the Brickstore example, APAC and AMER managers ask the same question yet receive different, authorized results, with regional rows, masked email values, and shared metric definitions; the source recommends testing by impersonating users and planning volume boundaries.
amazon.science
Modern language model architectures evolved around specific hardware constraints, but AWS Trainium chips alter memory and compute dynamics through on-chip SBUF memory, systolic matrix multiplication, and explicit DMA control. The AWS Trainium Frontier competition invites teams to train language models from scratch under strict wall-clock time constraints to uncover optimal architectures and custom kernels for Trainium silicon. Participants start from a fifty-million-parameter dense baseline and can modify everything from the model architecture and optimizer to custom Neuron Kernel Interface routines. Phase 1 evaluates thirty-minute single-chip training runs by validation bits-per-byte, while Phase 2 grants four-hour multi-chip server access to evaluate both training efficiency and reasoning on the CORE benchmark. Top finalists will present their findings at NeurIPS 2026, compete for cash prizes, and co-publish research with Annapurna Labs.
The best engineering reads, once a week.
