Understanding Business Architecture: Evolution, Challenges, and Practices

Business architecture, a concept over twenty years old, connects enterprise strategy with technical implementation and serves as a bridge between business and engineering teams; unlike reusable infrastructure, it must be tailored to each company's specific needs.

The interview with Jiang Junping, senior director at 58.com, covers the definition, characteristics, development stages, and challenges of business architecture, as well as its relationship with middle‑platforms and micro‑services.

Jiang’s background includes work at Microsoft and Tencent, leading large‑scale product development, and later overseeing infrastructure, cloud platforms, distributed storage, IM, and micro‑service middleware at 58.com, supporting billions of daily calls.

He describes business architecture as a complete set of technical solutions that achieve business goals, emphasizing qualities such as effectiveness, rapid delivery, sustainability, and low error rates.

As businesses grow, the scope of business architecture expands: small teams handle all concerns, while larger organizations separate general infrastructure (operations, storage, middleware, etc.) from domain‑specific business logic, often using middle‑platforms to avoid duplication.

The article traces 58.com’s evolution: starting with a Windows .NET monolith, migrating to Linux/Java with custom RPC and web frameworks, then reorganizing into business groups (BGs) after acquisitions, establishing a company‑wide technical middle‑platform for shared capabilities such as storage, search, AI, and security.

A key pain point is integrating disparate business architectures after mergers; 58.com unified the housing apps of 58.com and Anjuke by standardizing common components, refactoring code, and consolidating backend services, enabling a single codebase to serve both platforms.

The piece highlights the distinction between foundational infrastructure (generic cloud services, databases, middleware) and business architecture (domain‑specific assembly of those building blocks), noting that business architects must understand both the business domain and the technical characteristics of underlying components.

Successful business architects need solid technical foundations, strong communication, and the ability to abstract, layer, and simplify complex business scenarios, addressing concerns such as data scale, traffic, and strategy effectiveness.

Practical advice includes abstracting common business functions into a middle‑platform, considering data volume and access patterns, planning for future business changes, and making technology choices based on internal support, mature open‑source solutions, cloud provider offerings, or proven industry practices.

Finally, the article stresses that business architecture is not a one‑size‑fits‑all solution; it must continuously evolve with cloud, middle‑platform, and serverless trends, requiring architects to keep learning and adapting.