0 views collected around this technical thread.
This article explores six core software architecture patterns—Monolithic, Microservices, MVC, Controller‑Worker, Event‑Driven, and Layered—detailing their structures, typical use cases, advantages, and drawbacks to help developers choose the right design for scalable, maintainable applications.
This article explains Nginx's core Master‑Worker process model, high‑performance event‑driven design, I/O multiplexing with epoll, and asynchronous non‑blocking I/O, showing how these techniques enable the server to sustain millions of simultaneous connections.
This article explores how DeWu's community activity platform evolved from ad‑hoc implementations to a componentized, event‑driven backend using OOP principles, modular design, rule engines, and observer‑hook mechanisms, while also outlining future AI‑driven optimizations and system‑wide standardization.
This article explains the limitations of traditional I/O models, introduces epoll as a high‑performance Linux I/O multiplexing mechanism, details its design principles, API usage, kernel data structures, and provides practical coding examples and optimization tips for building scalable backend services.
epoll is a high‑performance Linux I/O multiplexing mechanism that replaces select/poll by using an event‑driven design with a red‑black tree and ready list, supporting edge‑ and level‑triggered modes, efficient data transfer via mmap, and providing superior scalability for high‑concurrency network applications.
This article describes a generic asynchronous processing SDK built on Spring that leverages transaction events, AOP, and a combination of Kafka, XXL‑Job, and MySQL to provide non‑intrusive, reliable, and idempotent async execution with configurable strategies, security levels, and monitoring dashboards.
The article explains how Domain‑Driven Design combined with microservice architecture can restructure a monolithic transaction system by defining bounded contexts, applying patterns such as layered architecture, CQRS and event‑driven communication, and refactoring domains to improve maintainability, scalability, and business clarity.
This article explains the fundamentals of event‑driven architecture, introduces Knative Eventing as a cloud‑native serverless framework, details its broker/trigger model, event sources, orchestration patterns such as Sequence and Parallel, and shows how to integrate it with Alibaba Cloud EventBridge while comparing it to KEDA.
This article explains how Nginx uses an event‑driven, asynchronous non‑blocking I/O model together with epoll/kqueue and various optimization strategies such as keep‑alive, caching, efficient data structures and load balancing to handle millions of concurrent connections in large‑scale internet architectures.
This article explains the fundamentals of Event‑Driven Architecture, covering its core components, design principles such as event granularity and immutability, practical implementation steps, common use cases, and the challenges developers face when building loosely coupled, high‑response distributed systems.
This article explains the concepts of level‑triggered (LT) and edge‑triggered (ET) event notification in Linux epoll, describes epoll's core data structures such as the red‑black tree and ready‑list, details the three main APIs (epoll_create, epoll_ctl, epoll_wait), and examines the locking and internal kernel mechanisms that enable efficient I/O multiplexing.
This article details the architecture, core component design, and implementation techniques of 58.com’s invitation business system, covering background, technical challenges, modular backend design, event‑driven services, rule‑engine filtering, protocol conversion, and process orchestration to improve scalability, efficiency, and reusability.
The article explains how microservice architectures handle inter‑service calls using RPC or event‑driven approaches, analyzes different coupling types, compares event notification with event sourcing, and offers practical guidance on API gateways, service composition, and when to choose each communication style.
This article explains the fundamentals of Domain-Driven Design (DDD), covering unified language, model abstraction, problem decomposition, aggregation, domain events, and how DDD principles translate into microservice architectures with practical code examples.
This article systematically explains epoll's core data structures—including a red‑black tree and a doubly linked ready list—its three main APIs, the kernel implementation details, thread‑safety mechanisms, ET vs. LT behavior, and how it improves over select/poll for high‑concurrency network programming.
The article explains the different types of coupling in microservice architectures, compares RPC and event‑driven communication—including event notification and event sourcing—discusses their trade‑offs, and offers practical guidance on choosing and combining these approaches for scalable backend systems.
The article explains how microservice systems handle service calls, compares RPC and event‑driven (message) communication, details various coupling types, discusses event notification and event sourcing, and offers practical guidance on reducing tight coupling through API gateways, versioning, and gRPC.
The article breaks down modern asynchronous programming by examining four core models—callbacks, Promises, reactive observer patterns, and message‑driven architectures—explaining their mechanics, pros and cons, and providing JavaScript/Dart examples and system diagrams to help developers master non‑blocking concurrency.
The article outlines emerging forces such as cloud, mobile, social, and big data that drive modern application architecture, advocates moving beyond traditional three‑tier designs, and recommends adopting service‑oriented, microservice, event‑driven, and open‑standard approaches while considering paradigms, models, and organizational structures.
This article explains every Spring Boot startup event, from ApplicationStartingEvent to ApplicationFailedEvent, showing when each occurs, how to customize them, and providing clear code examples to help developers extend and debug their applications effectively.