This article chronicles AutoHome’s five‑year journey of financial information system modernization, detailing the initial 2014 challenges, three development phases, the technical stack transitions, and the strategic outcomes that enabled unified finance operations and data‑driven management.
This article traces the evolution of enterprise distributed application architectures—from early SOA through microservices to modern cloud‑native and service‑mesh designs—explaining the underlying complexity challenges, architectural principles, and the trade‑offs that shape today’s agile IT systems.
The article examines the hype around the mid‑platform (中台) concept, explains its technical and organizational goals, outlines the engineering, data and innovation benefits, and then critically reveals the practical pitfalls such as cross‑cutting concerns, stability‑flexibility trade‑offs, unclear boundaries, human resistance, and cost‑center perception that limit its effectiveness.
This article explores the origins, architecture, and real‑world implementation experience of enterprise hybrid multi‑cloud, covering security solutions, resource pooling, IaaS/PaaS/SaaS layers, and common challenges such as data placement, network reliability, traffic routing, and standardization.
This article explains how a mid‑platform (中台) addresses core business challenges by enabling rapid support for new industries, reusing mature solutions, accelerating time‑to‑market, and requiring specific organizational structures, while also raising key questions about process orchestration, team composition, and data platform design.
The article examines how the rise of cloud platforms, micro‑services, big data, AI and IoT is driving enterprises to replace decade‑old client‑server architectures with cloud‑centric, real‑time systems across retail, manufacturing and finance, outlining the technical and operational shifts required for digital transformation.
This article outlines the development of enterprise business architecture—from early models like Zachman and TOGAF to modern frameworks such as FEA and DODAF—defines its purpose as a structured capability analysis that bridges business strategy and IT implementation, and explains its role in digital transformation and its interplay with various IT architecture layers.
This article explores the concept of the middle platform in Chinese tech firms, tracing its roots from Supercell’s game development model to Alibaba’s 2015 restructuring, examining how companies like Tencent, Baidu, and JD implement middle platforms, the pain points they address, the types of middle platforms, design principles, and criteria for enterprises considering adoption.
When creating software or solution architecture diagrams, it is essential to consider layered structures, platform and service distinctions, SOA principles, and the separation of application and technical views to effectively communicate enterprise‑wide or single‑system designs.
This article explores the concept of the mid‑platform (ZhongTai) as an enterprise‑level capability‑reuse platform, explaining why companies adopt platformization, the distinction between front‑end, back‑end and mid‑platform, various types of mid‑platforms, and practical guidance for building and evaluating them.
Alibaba’s Entertainment Group, led by senior director Wei Zhou, is building a dedicated mid‑platform that consolidates heterogeneous subsidiaries like Youku and UC, leveraging shared data and middleware to cut development costs, improve agility, and support future 5G, AI, and VR/AR innovations.
The article explains how modern enterprises can achieve adaptive integration by applying Gartner's Pace‑Layered architecture, categorizing applications into record, differentiation, and innovation layers, and using Microsoft services such as Azure Service Bus, Logic Apps, and BizTalk to manage governance, change control, and messaging across these layers.
The article analyzes the mid‑platform (Zhongtai) concept—its military origins, how it standardizes business rules, improves efficiency, and enables rapid user‑centric responses—illustrated with Alibaba, Haier, and Huawei case studies, and discusses benefits, challenges, and practical recommendations for enterprises.
The article explains what a data middle platform is, why it differs from data warehouses and data platforms, outlines its core capabilities, discusses the strategic and tactical considerations for building one, and examines the organizational, technical, and privacy challenges involved in its adoption.
The article explains the origin and evolution of the mid‑platform concept, why enterprises adopt platformization, showcases examples such as Alibaba, Haier and Huawei, describes various platform types (business, data, mobile, technical, R&D, organizational), and outlines its benefits, challenges, and practical recommendations for digital transformation.
This article explores the concept of the “mid‑platform” (中台), explains why enterprises pursue platformization, distinguishes front‑end, back‑end and mid‑platform roles, and shows how a well‑designed mid‑platform bridges speed and stability to boost user‑centric innovation.
The article explains the origin, purpose, and multiple implementations of the mid‑platform (business, data, technical, R&D, and organizational) in modern enterprises, illustrating how platformization improves user response, reduces duplication, and supports digital transformation while highlighting the challenges and recommended practices.
At the GITC 2018 conference, Suning’s IT executive shares how a trust‑based, product‑oriented R&D management approach built on Suning Cloud enables massive scale, continuous delivery, and a high‑performance team to drive the retailer’s digital transformation.
The article details Suning’s Internet‑plus transformation, describing its strategic “one body, two wings, three clouds, four ends” model, the evolution of its enterprise architecture across three generations, the adoption of cloud, SOA, micro‑services, big‑data and AI platforms, and the accompanying R&D and organizational reforms.
This article reviews core database high‑availability technologies—including DB2 HADR, SQL and Q replication, HACMP clustering modes, DPF limitations, and storage‑level disaster‑recovery solutions—explaining their mechanisms, suitable scenarios, and practical deployment considerations.
The article explains how Alluxio provides a virtual distributed file system that acts as a "virtual data lake," enabling unified, high‑performance access to structured and unstructured data across heterogeneous storage back‑ends while reducing storage costs through intelligent caching and eliminating the need for permanent data copies.
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.
Master data refers to high‑value core business entities such as customers, products, and accounts that are shared across multiple systems, and master data management (MDM) provides the standards, technologies, and processes to collect, integrate, cleanse, govern, and distribute this data consistently throughout an organization, improving data quality, compliance, and agility.
This guide walks you through defining clear objectives, identifying key business problems, selecting appropriate frameworks, modeling essential domains, creating a meta‑model, and integrating and analyzing your enterprise architecture, offering practical tips, examples, and best‑practice recommendations to ensure your EA project succeeds.
Explore ten common software architectural patterns—including layered, client‑server, master‑slave, pipe‑filter, proxy, peer‑to‑peer, event‑bus, MVC, blackboard, and interpreter—detailing their structures, typical use cases, advantages, and drawbacks, to help you choose the right architecture for enterprise‑scale systems.
This 2017 survey‑based report analyzes why traditional enterprises are turning to microservices, examines their adoption levels, challenges, Docker usage, emerging Service Mesh technologies, and offers practical guidance for planning and implementing microservice architectures in legacy IT environments.
Suning’s 2018 strategic shift transformed its traditional IT department into a technology group that integrates cloud computing, big data, AI, micro‑services and containerization across eight business units, driving a data‑driven, smart‑retail ecosystem and scaling its IT workforce to support rapid innovation.
The article explores the distinction between part‑time and full‑time software architects, outlines the core responsibilities such as global technical planning, unified methods and standards, robust foundational building, and practical implementation, and discusses rights, assessment criteria, and practical ideas for effective architecture practice.
This article explains how a high‑traffic e‑commerce platform uses RabbitMQ for reliable, high‑throughput order processing, covering its core concepts, routing patterns, clustering, high‑availability queues, client support, management tools, and step‑by‑step cluster deployment.
This article outlines a comprehensive enterprise SOA strategy, detailing the design of an ESB with core functions, component architecture, and a product development platform that enables modular, reusable business components across systems.
This article explains how DevOps extends beyond bridging development and operations to create a complete, closed‑loop management system that boosts engineering efficiency, supports product and project lifecycles, and enables scalable, automated delivery for enterprise digital transformation.
Alibaba’s transformation from e‑commerce leader to tech powerhouse is highlighted by its Feitian middleware platform, a cloud‑based, highly available solution that supports diverse industries, enables massive transaction volumes, and exemplifies the evolution of large‑scale distributed architectures pioneered since Alibaba’s early IOE days.
This article explains how to build enterprise‑grade business components (BC) within a Service‑Oriented Architecture using Web services, OSGi modularity, and an Enterprise Service Bus, covering component models, granularity, loose‑coupling design, interface standards, and J2EE deployment patterns.
This article shares the author’s multi‑year experience in cloud computing, covering the evolution of cloud platforms, the relationship between microservices and DevOps, the design of a Kubernetes‑based DevOps platform, and practical lessons for enterprise‑level adoption.
The article examines various messaging patterns—Message Channel, Publisher‑Subscriber, Message Router, and others—explaining their principles, advantages, and implementation details, and illustrates their use in enterprise distributed architectures through concrete code examples and case studies such as CIMS and a medical system.
This article examines VIPshop’s business model evolution and the technical transformation of its e‑commerce platform, detailing the shift from a single‑application LAMP monolith through vertical and distributed architectures to a cloud‑native, service‑oriented design, and outlines the key governance, scalability and operational challenges addressed along the way.
This article recounts Credit Suisse’s 15‑year evolution from tightly coupled mainframe applications to an open SOA service bus, highlighting the importance of interface contracts, service management, and the challenges of large‑scale integration in a global banking environment.
The article details how Alibaba Cloud's multi‑layered enterprise architecture, built on service‑oriented frameworks, distributed databases, and message queues, enabled record‑breaking Double 11 transactions while offering linear performance scaling, high reliability, and cost‑effective operations for large‑scale internet applications.
Industry veterans outline ten pivotal concepts—from Industry 4.0 and “Internet+” to microservices, distributed systems, big data, multi-screen integration, Docker, OpenStack, and platform‑microapp strategies—highlighting how enterprise software architecture is evolving toward more agile, loosely‑coupled, cloud‑native ecosystems.
The article distills ten pivotal keywords—Industrial 4.0, Internet+, BFV, microservices, distributed systems, big data, multi‑screen fusion, Docker, OpenStack, and large‑platform micro‑apps—explaining how each shapes the evolution of enterprise software architecture and what challenges and opportunities they bring.
This article traces the historical origins of architecture from Vitruvius’s ancient treatise to contemporary IT frameworks such as Zachman, TOGAF, and FEA, explains core definitions, compares various architect roles, and offers practical guidance on applying architectural frameworks to drive enterprise transformation and operational efficiency.
