Unlocking IT Architecture Governance: From Theory to JD.com’s Real‑World Success

1. What Are Architecture and Governance

1.1 Origin of Architecture

Architecture originally comes from the Latin word for building and was first used to describe the physical structures of civilization. Over time, the idea of summarizing complex scenarios into simple, logical structures was applied to IT, where software development resembles building a wall with bricks. As systems grew, the need for architectural thinking emerged to avoid repeated fixes and redesigns.

1.2 Architecture and Governance

Governance follows architecture. While governance is a specialized form of management that adds processes, practices, rules, and relationships, it is typically initiated by senior leadership and can be either phased or long‑term. Its value lies in balancing benefits, risks, and resource investment.

2. Main Standard Systems for IT Architecture Governance

International standards such as COBIT (originating from COSO), ITIL, ISO/IEC 17799, and CMMI provide frameworks for IT risk management, service delivery, and security. In modern enterprises, these standards are combined with cloud, big data, and AI capabilities.

2.1 COBIT

COBIT is a globally recognized IT management and control framework that defines 34 processes grouped into four domains: Planning & Organization, Acquisition & Implementation, Delivery & Support, and Monitoring. Governance activities are placed in the EDM (Evaluate, Direct, Monitor) domain.

2.2 ITIL

ITIL provides a measurable, objective standard for IT service management, covering the service lifecycle (strategy, design, transition, operation, continual improvement) and ensuring alignment between IT and business.

2.3 IT4IT Reference Architecture

IT4IT, from The Open Group, describes a value‑chain‑oriented reference architecture that enables seamless information flow across the entire IT value chain, helping organizations deliver maximum value at minimal cost.

3. IT Architecture Governance Methods

Governance must align with enterprise strategy and cover the full lifecycle of architecture, including design, change, iteration, and retirement. Key components include organization and personnel, principles and standards, activities, culture and ethics, and supporting tools.

3.1 Organization and Personnel

The governance body defines architecture principles, review standards, design processes, and change‑management procedures. It also establishes a charter, collaboration mechanisms, and performance metrics.

3.2 Principles and Standards

Consistency, high cohesion & low coupling, SMART goals.

Business‑centric, value‑driven governance.

Encourage innovation and change.

Maintain stability while evolving architecture.

Standardization and risk mitigation.

Focus on non‑functional goals such as flexibility, stability, and scalability.

3.3 Culture, Ethics, and Behavior

Building a culture where architects understand the broader impact of their decisions, share responsibility for quality, and act with professional ethics is essential for sustainable governance.

3.4 Tools

Governance tools are divided into two groups: the assets being governed (infrastructure, platforms, services) and the tools that enable governance (project‑management systems, monitoring platforms, knowledge‑management portals, architecture repositories).

4. JD.com IT Architecture Governance Practice

4.1 Technical‑Business Integration

JD.com faced two challenges: supporting massive, multi‑business growth and avoiding duplicated effort. By adopting a cloud‑native, micro‑service‑based infrastructure and a business‑technology integration platform, JD achieved rapid resource provisioning, cost reduction, and agile development.

4.2 IT Architecture Committee

The committee drives stability, cost reduction, technical innovation, and influence. Its responsibilities include fault post‑mortems, architecture reviews, stability projects, cost governance, process improvement, technical risk assessment, and external technology promotion.

5. Conclusion

Effective IT architecture governance requires senior‑level commitment, cross‑department collaboration, and hands‑on execution. It elevates the role of architects, safeguards business value, and guides continuous improvement. This article aims to clarify common confusions and provide a practical roadmap for technology teams.