E‑commerce, SaaS, AI architect; DDD enthusiast; SKILL enthusiast
This article compiles core architectural concepts—including ROI, SOLID principles, system splitting, isolation, ACID, CAP/BASE, distributed transactions, and capacity estimation—explaining their definitions, practical examples, trade‑offs, and how they guide architects in making informed technical decisions.
This article walks through Domain‑Driven Design fundamentals, distinguishes strategic and tactical design, introduces the four‑color modeling archetypes, and demonstrates their application in an e‑commerce microservice case study, highlighting how DDD bridges business requirements and code architecture.
The article revisits the CAP theorem, explains linearizable consistency and strict availability, demonstrates with concrete data‑center examples why the CP/AP split is often misleading, and argues that latency concerns and broader failure modes make the binary classification of distributed systems impractical.
This article breaks down how MySQL's InnoDB engine guarantees the four ACID properties—atomicity, consistency, isolation, and durability—by leveraging undo and redo logs, the binary log, hidden transaction metadata, and MVCC with ReadView, illustrating each mechanism with concrete examples.
The article breaks down Spring's circular dependency problem, explains its three typical forms, details the three‑level cache mechanism with code snippets, walks through the step‑by‑step resolution process, and lists scenarios where Spring cannot resolve such dependencies.
In this interview‑style tutorial, an Alibaba P7 engineer walks through the limitations of BIO, the non‑blocking NIO API, kernel‑level select/poll mechanisms, and the design of epoll, illustrating how each solves the C10K problem and how they are used in Java.
The article explains how breaking a monolith into microservices can introduce data consistency challenges, discusses the CAP theorem and Conway's law, and provides practical guidelines—such as single‑responsibility division, team‑aligned service boundaries, and appropriate use of BASE and distributed transactions—to split services responsibly.
The article explains how to achieve 100% message delivery and consumption in MQ systems by covering producer acknowledgments, broker persistence mechanisms, and consumer idempotency, with detailed comparisons of RabbitMQ and Kafka implementations and configuration tips.
The article explains the company's B2B vertical e‑commerce model, outlines its core service modules, compares B2B and C2C commerce, and details the Java‑based microservice architecture, high‑availability design, and ongoing recruitment efforts.
The article walks through Redis’s two persistence options—RDB snapshots and AOF logs—detailing how each works, their advantages and drawbacks, and why interviewees should understand their differences, including AOF rewrite compression, to answer interview questions accurately.
