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
Endianness dictates the order in which multi-byte numbers are stored and transmitted across systems. While big-endian formats store the most significant byte first at the lowest address, little-endian systems place the least significant byte first. Communication across diverse architectures relies on consistent byte ordering to prevent critical interpretation errors in fields such as telecommunications, IoT, automotive, finance, and aerospace. To safely process disparate payloads, modern ingestion pipelines deploy an endian converter to normalize raw binary data into a unified format. These normalized data streams flow through Apache Kafka, undergo real-time processing and enrichment via Atlas Stream Processing, and persist in MongoDB Atlas for downstream analytics and visualization.
Enterprise AI agent initiatives frequently stall after pilot phases due to technology-first thinking, governance gaps, infrastructure complexity, and poor alignment with business needs. To bridge this divide, development teams are shifting away from data-first pipelines toward a product-first methodology structured as product, agent, data, and model. The Canvas framework provides a phased workflow moving from quick proof-of-concept validation to model orchestration and operational hardening. In Phase 4, developers focus on API management, external provider orchestration, cost optimization, and evaluation pipelines. Phase 5 adds necessary governance, compliance, user experience, and security layers required to transform working agent prototypes into sustainable production deployments.
Organizations building generative AI applications require simplified, standardized connections to an expanding ecosystem of enterprise databases. MCP Toolbox for Databases, an open-source Model Context Protocol server based on Anthropic's standardized protocol, now supports MongoDB Atlas to streamline connections to generative AI systems. This new integration allows gen AI agents to execute standard CRUD operations alongside advanced transformations and computations using the MongoDB aggregation framework. Through flexible configuration files, developers can configure MongoDB Atlas as both a data source and a sink by defining parameters like connection URIs, target datasets, filters, projections, and toolsets. By linking flexible document data with cross-database query capabilities, enterprises can unify results and automate multi-source AI workflows.
Migrating core insurance platforms from legacy relational databases with PL/SQL to Java and MongoDB Atlas frequently degrades batch processing performance. Like-for-like migrations can cause batch jobs to run 25 to 30 times slower due to high network round-trips, inefficient per-record operations, and under-utilized bulk capabilities. To resolve these bottlenecks, an optimization framework was developed that leverages MongoDB native bulkWrite operations, intelligent reference data prefetching, and parallel execution. An architecture combining a Spring Boot controller and a dedicated executor framework partitions workloads across threads or event processors. This framework recovered lost performance, completing previously failing batch jobs within service-level agreements and achieving 10 to 15 times better execution speeds than legacy systems in certain workloads.
At MongoDB.local NYC 2025, MongoDB introduced new capabilities and product updates tailored for artificial intelligence workloads. MongoDB 8.2 was unveiled alongside public previews of full-text and vector search for both MongoDB Community Edition and Enterprise Server. The company also detailed its integration with Voyage AI embedding and reranking models to deliver precision retrieval across raw data, metadata, and vectors. To address legacy infrastructure migration hurdles, MongoDB launched the Application Modernization Platform, which combines AI-assisted tooling and specialized workflows to accelerate legacy application refactoring two to three times faster. These architectural updates aim to position the JSON document model as the persistent memory and context store required by autonomous, agentic AI workflows.
At the MongoDB.local NYC 2025 event, MongoDB unveiled several platform updates aimed at modernizing enterprise database architectures and supporting emerging agentic artificial intelligence workloads. The newly released MongoDB 8.2 version provides enhanced performance alongside expanded developer features across the broader document database ecosystem. The company also integrated Voyage AI embedding and reranking models to improve context retrieval precision and efficiency when building production-grade AI systems. Furthermore, dedicated Search and Vector Search capabilities have reached general availability across both MongoDB Community Edition and Enterprise Server environments. To streamline infrastructure transitions, the newly introduced Application Modernization Platform leverages AI-powered tooling and specialized techniques to migrate legacy database systems two to three times faster.
MongoDB unveiled several core database updates aimed at supporting artificial intelligence workloads during MongoDB.local NYC 2025. The release of MongoDB 8.2 introduces performance enhancements alongside Voyage AI embedding models and rerankers for AI applications. Furthermore, Search and Vector Search are now available in public preview for both MongoDB Community Edition and MongoDB Enterprise Server. To address the costs and operational friction of legacy systems, MongoDB launched the Application Modernization Platform (AMP), which combines AI-powered tools with specialized talent to accelerate database migrations. These capabilities position the JSON-based document model to supply the persistent state, memory, and retrieval mechanisms required by emerging agentic AI architectures.
MongoDB announced several product releases and platform updates aimed at supporting artificial intelligence and agentic workflows at MongoDB.local NYC. The release of MongoDB 8.2 arrives alongside integrations with Voyage AI embedding and reranker models designed to enhance data retrieval precision. In addition, MongoDB launched Search and Vector Search in public preview for both Community Edition and Enterprise Server deployments, bringing vector capabilities to self-managed environments. To assist organizations transitioning away from rigid legacy database systems, MongoDB also introduced the Application Modernization Platform, which combines AI-driven tooling and specialized migration expertise. Early benchmarks from the modernization platform demonstrate legacy migrations running two to three times faster while accelerating code rewriting tasks by an order of magnitude.
Stripe built a real-time streaming analytics system for Billing after customers said they needed to detect emerging behavior and adapt pricing quickly, replacing a batch pipeline whose subscription updates lagged by 24 hours on average. The architecture uses Apache Flink to maintain compressed subscription history and incrementally process analytics events, while a custom Apache Spark job generates initial Flink state from billions of historical events and supports validation and exports. A new Apache Pinot v2 query engine performs windowed aggregations and joins without offline preaggregation; most updates are processed in under one minute, nearly all reach users within 15 minutes, and production query latency is under 300 milliseconds. Metric-definition changes trigger historical recalculation while new events are buffered and later replayed, preserving a consistent Dashboard view during the transition.
Stripe events can connect backend state changes to responsive frontend interfaces for payments, subscriptions, connected accounts, and Stripe Terminal workflows. The post contrasts polling, which can increase traffic, latency, and delta-computation complexity, with push subscriptions, while noting that a hybrid of initial API loading and incremental updates is common. It describes webhook endpoints and Amazon EventBridge as ingestion choices, then emphasizes idempotency, ordering, duplicate detection, and failure handling. Frontend delivery options include WebSockets, MQTT, gRPC, Server-Sent Events, polling, AWS AppSync, and Momento, selected according to messaging pattern, direction, latency, scale, and operational trade-offs. An abbreviated lounge example uses a PaymentIntent and Terminal reader, routes payment_intent.requires_payment_method through EventBridge to AWS AppSync Events, and lets a React client mark the reader ready to collect payment.
Shopify successfully migrated two largest apps, Shopify Mobile and Shopify Point of Sale, to React Native’s New Architecture while continuing weekly releases for millions of merchants. The strategy prioritized minimal code changes, dual-architecture compatibility, and performance and stability parity, with TopHat generating both architecture builds for every pull request. The team upgraded React Native first, updated or removed incompatible dependencies, and changed only native modules that failed under the new architecture rather than migrating all 40-plus modules to TurboModules. Migration issues included state batching, UIManager-related blank screens, shadow-tree manipulation, view flattening, and main-thread legacy module initialization; the reported outcome was maintained development velocity with no feature-development disruption, followed by planned optimization work.
Online marketplaces connect buyers and sellers while monetizing commissions, shipping, marketing, payment operations, insurance, or other value-added services. Greens & Dairy Mart illustrates a model in which farmers receive payment after delivery, sellers pay a 15% rate on sales, and shipping, marketing, payout, and insurance options create additional revenue streams. Stripe Connect supports transaction-linked fees through the Platform pricing tool or application_fee_amount, while Stripe Billing provides usage-based meters, subscriptions, and invoices for recurring or one-off charges. The example records pay-per-click, conversion, and penalty events against farm customers, charges monthly subscriptions automatically, and bills damaged-goods insurance annually, with the stated conclusion that programmatic disbursement and monetization give marketplaces a central point to monitor and report these activities.
Shopify’s Sidekick evolved from a simple tool-calling system into an agentic assistant that helps merchants manage stores through natural language, exposing scaling challenges in architecture, evaluation, and training. As its inventory grew beyond 50 tools, the system prompt accumulated conflicting special cases and became difficult to maintain; JIT instructions instead return relevant guidance with tool data. For evaluation, the team uses Ground Truth Sets based on production distributions, human labels from at least three product experts, statistical agreement measures, specialized LLM judges calibrated against humans, and merchant simulation. Judge correlation rose from Cohen’s Kappa 0.02 to 0.61 against a human baseline of 0.69, while syntax validation improved from about 93% to 99% after reward-hacking fixes. GRPO training exposed opt-out, tag, and schema hacking, and the post recommends modularity, procedural plus semantic validation, user simulation, and iterative judge refinement for production agentic systems.
Maintaining consistent product data between an internal catalog and Stripe becomes difficult when outages, throttling, high volumes, and changes from both systems create reconciliation failures. The post compares a naive one-way flow, in which a Lambda calls the Stripe API with no persistent synchronization record, with a queue-based design that durably stores changes, controls processing rate, retries failures with exponential backoff, and sends persistent failures to dead-letter queues. For bidirectional synchronization, it contrasts periodic ETL, using extraction, transformation, and loading, with an event-driven model based on Stripe Event Destinations, EventBridge, SQS, and symmetrical events from internal systems. The conclusion is that durable, observable queues and event-driven processing provide buffering, auditability, near-real-time propagation, independent change processing, and more graceful scaling for distributed reconciliation.
Keeping internal product data aligned with Stripe becomes an architectural challenge as catalogs grow from hundreds to millions of items. The problem spans independently operated systems with different data models, API constraints, rate limits, availability guarantees, and consistency models, while products may change faster than periodic reconciliation can complete. Stripe's payment-focused model covers identifiers, descriptions, prices, currencies, billing terms, and subscription behavior, whereas internal systems may contain categories, inventory, rich content, technical specifications, media, and sensitive cost data. The series examines manual verification, simple scripts, and periodic jobs for smaller catalogs, then points to streaming, change data capture, intelligent partitioning, and conflict resolution for high-scale reconciliation. It concludes that cross-system synchronization requires deliberate mapping and automated architecture because perfect synchronization is difficult to guarantee in eventually consistent distributed systems.
The post presents a gym membership access system that replaces plastic cards, fobs, and physical keys with Apple Wallet and Google Wallet passes scanned by an NFC reader. It uses Stripe Checkout and subscriptions for payment, PassNinja as a single API layer for issuing passes, and a DotOrigin VTAP100 connected to a Raspberry Pi Zero 2W, relay, and door strike for entry control. After Checkout, the website verifies that the Stripe subscription is active, creates a pass whose nfc-message contains the Stripe subscription ID, and redirects the member to add it to a wallet. A Linux gate process reads that identifier from the reader's virtual serial port, retrieves the subscription from Stripe, and activates the relay for five seconds when the status is active; otherwise it denies access.
Portia AI presents a customer-refund agent that combines its guardrails with Stripe’s official Model Context Protocol server. The agent reads a refund request, compares it with a policy file, identifies the relevant Stripe customer and payment intent, and evaluates whether the request should be approved. Portia’s planner produces a multi-agent plan, while execution agents run it and persist outputs in plan state; an execution hook pauses before the Stripe create-refund call. A clarification presents the request and the agent’s rationale to a human, who can approve it in the CLI; approval allows the refund to proceed, while rejection exits without creating one. The example also handles Gmail OAuth and can send the customer an email describing the outcome.
The article presents “second-order automation,” in which one agent designs reusable workflows for another agent to execute. Its spreadsheet system pairs an “architect” that watches a screen recording, generates detailed prompts, identifies required files and context, with a “doer” that searches workbooks and performs the instructions. The design addresses first-order automation’s dependence on users to supply precise prompts and fresh context for every task, which limits scalability. On an approximately 50-task SpreadsheetBench subset, the spreadsheet agent reached 49.5% accuracy on soft-restriction tasks versus OpenAI’s 45.5%, and 32.5% on hard-restriction tasks versus GPT-4o’s 13.4%; some one-to-two-hour tasks finished in under 10 minutes. The article concludes that recorded workflows can let non-technical users create reusable automations with little additional input, although architect performance has not yet been formally benchmarked.
Canva engineers developed and shipped a real-time drawing tool for presentation mode after user feedback highlighted it as a highly requested feature. Integrating the existing editor-bound draw functionality into presentations required resolving tight package coupling, dual-window scaling mismatches, and performance regressions. To overcome architectural boundaries, core draw logic was extracted into a shared common package using interface abstractions. Coordinate normalization resolved positioning and scaling differences across presenter and audience views, while code-splitting deferred loading the core engine until activation. As a result, presentation load time regression dropped from 7% to 0.24%, and the feature reached over 470,000 monthly active users in production.
Model Context Protocol (MCP) can let AI agents search catalogs, interpret reviews, build carts, and support purchases, but a text-only flow does not provide the visual and interactive details central to commerce. Shopify presents MCP UI as an extension that returns embedded UI resources for components such as product cards, with delivery through inline HTML, remote resources in sandboxed iframes, or Remote DOM. Its intent-based message system keeps components from directly modifying state: actions such as view_details, checkout, notify, and ui-size-change are surfaced for the agent to interpret, while render data lets hosts provide CSS for adaptive styling. The open-source, deliberately extensible protocol is demonstrated in a Shopify Storefront MCP UI Server prototype and is intended for commerce as well as data visualization, form builders, and media players.
The best engineering reads, once a week.
