Software Architecture and System Design News
Latest curated articles from top engineering blogs
Shopify
AWS132 articles
Airbnb's Privacy-First Social Features: User and Profile Separation
Airbnb designed new social features with privacy at their core by distinguishing between internal User IDs and context-specific Profile IDs. This architectural decision enables granular control over data visibility, allowing users to customize their public presence for different experiences while preventing inadvertent data correlation. The implementation involved extensive code auditing, permission management via an in-house authorization system, and company-wide collaboration.
Architecting Gen AI Applications in Java: A Framework Comparison
This article compares leading Java Generative AI frameworks for 2026 – Genkit Java, Spring AI, LangChain4j, and Google ADK Java – from an architectural perspective. It highlights their design philosophies, abstraction levels, integration patterns, and trade-offs, which are crucial for architects deciding on the right framework for production-grade AI systems. Understanding these differences informs decisions around observability, scalability, and developer experience in AI-driven Java applications.
Conceptual Integrity in System Design: Lessons from The Mythical Man-Month
This article highlights the enduring relevance of Fred Brooks's _The Mythical Man-Month_ in software development, particularly emphasizing Brooks's Law on adding manpower to late projects and, crucially, the importance of conceptual integrity in system design. It argues that a system's coherence and consistency, driven by a single set of design ideas, are paramount for its success and long-term maintainability, even if it means omitting some features.
Airbnb's Skipper: An Embedded Workflow Engine for Durable Execution
Airbnb developed Skipper, an embedded workflow engine, to address the challenges of durable execution for long-running, multi-step business processes. It provides reliable, exactly-once semantics and crash recovery without the operational overhead of external orchestration clusters or the vendor lock-in of cloud-managed services. Skipper's design focuses on simplicity, embedding within services, leveraging existing infrastructure, and enabling developers to write business logic cohesively.
Building Real-time AI-Driven Systems with Event-Driven Architecture
This article outlines a practical system design pattern for building real-time applications that balance user responsiveness with heavy backend processing, particularly involving AI/ML. It leverages an event-driven architecture using Spring Boot for event production, Kafka for asynchronous processing and decoupling, and WebSockets for real-time delivery of AI-analyzed insights to users.
Solving the DPoP Storage Paradox in Browser-Based OAuth Systems
This article explores the architectural challenges of securely storing private keys for DPoP (Demonstrating Proof-of-Possession) in browser-based applications, a critical component for preventing OAuth token replay attacks. It highlights the "storage paradox" where browser mechanisms like IndexedDB, while preventing key extraction, still allow XSS attacks to use the key as a signing oracle. The discussion then focuses on the Backend-for-Frontend (BFF) pattern as the industry standard solution for shifting key management server-side, outlining its benefits and trade-offs.
The Pillars of Modularity in System Design
This article explores the concept of modularity in software architecture, defining it as autonomous, interchangeable units with clear boundaries and explicit interfaces. It highlights how modularity lowers the cost of change over time and enhances reusability, illustrating these principles through diverse examples like Docker, Module Federation, and Notion.
Implementing a Circuit Breaker for AI Tool Calls to Prevent Cascading Failures
This article details the design and implementation of an MCP (Multi-protocol Communication Protocol) circuit breaker to prevent cascading failures in AI agent workflows. It focuses on how the circuit breaker pattern, a key distributed systems concept, can be applied to isolate flaky external tool calls and ensure system resilience. The post explores the state machine, failure handling, and configuration for robust operation at scale.
Architectural Strategy for Migrating Legacy Database-Centric Systems with Event Sourcing
This article outlines an architectural strategy for migrating legacy database-centric systems using events and progressive ownership transfer. It focuses on how to incrementally modernize monolithic applications by extracting functionalities and data, leveraging event-driven patterns to decouple services and manage data consistency during the transition.
Smart Client SDK: Decoupling Frontend State & API Interactions for Enterprise Architecture
This article introduces the "Smart Client SDK" pattern, advocating for robust client-side architecture in enterprise B2B systems. It details a "Librarian/Menu" approach to decouple API fetch logic and state synchronization from UI components, promoting maintainability, testability, and framework independence.
Optimizing Large Pull Request Diffs at Scale
GitHub Engineering details their strategies for improving the performance of the 'Files changed' tab, particularly for large pull requests. This involved a multi-pronged approach combining component-level optimizations, UI virtualization, and broader rendering improvements to reduce DOM nodes, memory usage, and interaction latency, showcasing practical front-end architecture for highly interactive web applications at scale.
EmDash: A Serverless, Secure Plugin Architecture Successor to WordPress
EmDash is presented as a modern, serverless alternative to WordPress, addressing critical security and scalability limitations. Its core architectural innovation lies in a sandboxed plugin model using isolated Dynamic Workers, which significantly enhances security and developer flexibility. The system also leverages serverless functions for efficient, scalable hosting with a pay-per-use payment model for content.