1 views collected around this technical thread.
The article examines the challenges of interface placement, service dependencies, and client-specific adaptations in a complex supply‑chain system and proposes an API aggregation layer and Backend‑for‑Frontend (BFF) pattern, detailing implementation with Spring Cloud and practical team division.
The article examines the practical difficulties of integrating services within a microservice architecture—such as circular dependencies, third‑party system coupling, and non‑idempotent APIs—and proposes concrete design principles like one‑way dependencies, minimal redundant data, façade services, idempotency, and contract testing to preserve system health.
The Metadata Center, built by Alibaba Entertainment, streamlines development by offering a searchable Data Source Plaza and a configurable Custom Interface engine that abstracts service calls, adds unified monitoring and circuit‑breaker safeguards, and leverages optimized scripting, cutting upfront coding effort and accelerating feature delivery across Youku applications.
Alibaba migrated Xianyu Coin’s points from the legacy KingTower platform to the new Banliang service using a four‑phase, service‑based approach—preparation, active/passive data migration with distributed locks, dual‑write for consistency, reconciliation, and a gradual service switch—completing the transition in a month without user impact.
This article analyses the shortcomings of fragmented operations platforms, explains how organizational and business domain factors shape a successful ops middle platform, and presents a lifecycle‑driven, multi‑layer integration approach for building a scalable, cloud‑native operations ecosystem.
The article examines the challenges of traditional SOA and microservice architectures in large enterprises, proposes a distributed multi‑center integration model that combines traditional services with microservices, emphasizes security, scalability, and data redundancy, and outlines the roles of capability centers, open platforms, and routing components within a cloud‑native environment.
This article outlines the design and implementation strategy for a business platform, focusing on integrating sales, services, and processes to enhance operational efficiency and achieve business goals.
The article examines how enterprises can combine traditional service systems with micro‑services by adopting a distributed multi‑center architecture, emphasizing versioning, non‑intrusive integration, security constraints, partitioned ESB clusters, data redundancy, and cloud‑native deployment to achieve a balanced, scalable, and secure service ecosystem.
The article describes JD's TESB (Decare) platform, explaining how it evolves from traditional ESB by applying BPM concepts to create a low‑code, semi‑decentralized service bus that improves integration efficiency, scalability, and performance through non‑blocking I/O, asynchronous processing, and virtual isolation mechanisms.
The article recounts Youzan’s transition from a Koa‑based internal system to the Astroboy framework—first version for decoupling code, then Astroboy 2.0 built on Koa2 with a customizable upper‑layer Base Framework, extensible plugins, and a Go‑based Tether proxy that streamlines Node‑to‑Java service integration and improves performance.
This article explains the microservices architecture style, compares it with monolithic and SOA approaches, outlines design principles, communication mechanisms, data decentralization, integration patterns, and discusses the advantages and disadvantages of adopting microservices in modern software systems.
This article details the challenges, architectural evolution, key components, implementation experiences, and future directions of Ctrip's operations workflow platform, illustrating how a multi‑stage, layered design and standardized services have transformed manual IT operations into an automated, observable, and scalable system.