Why “Business Identity” Is the Key to Scalable Platform Architecture

When a platform reaches a certain scale, further improvement requires solving the "business identity" problem: uniquely marking each request with meaningful business attributes rather than a simple transaction ID.

1 Business Identity Value

Scalability Dimension

Scalability

With a business identity, developers can add new strategies without altering the core transaction flow, allowing a dedicated team to maintain the engine and ensuring high extensibility. The platform can offer generic services while also providing extension points that are triggered based on the business identity.

Deployment Dimension

Deployment

Business identity enables cluster‑level deployment per business dimension. When a service supports multiple scenarios, upgrades can be performed selectively on the clusters that serve the affected business identity, reducing the risk of cross‑scenario failures.

Monitoring Dimension

Monitoring

Global or business‑specific call‑chain dashboards can be built using the business identity, allowing early detection of issues in low‑traffic or new business lines that would otherwise be invisible in pure technical metrics.

Stability Dimension

Stability

Business identity permits differentiated QoS policies, performance baselines, and traffic throttling per business, making it possible to isolate performance degradation and apply targeted remediation during high‑traffic events.

2 Further Understanding of Business Identity

Single‑Dimension Element

A business identity is a unique identifier for a business or scenario, often expressed as an enum or string (e.g., "pcLogIn", "appLogIn", "wechatLogIn").

Multi‑Dimension Elements

Complex scenarios may combine dimensions such as product, merchant, or channel. The identity must remain globally unique across the platform, acting like a tenant identifier that also drives routing, monitoring, and rule configuration.

3 Open‑Source Framework Examples

Eclipse Platform "Business Identity"

Eclipse uses the <nature> tag in the .project file to declare the project type (e.g., Java, Maven). This tag functions as the platform's business identity, allowing the IDE to apply the correct build and execution pipelines.

<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
    <name>Test</name>
    <comment/>
    <projects/>
    <buildSpec/>
    <natures>
        <nature>org.eclipse.jdt.core.javanature</nature>
        <nature>org.eclipse.m2e.core.maven2Nature</nature>
    </natures>
</projectDescription>

COLA Framework

COLA defines three dimensions for business identity:

Business : a profit‑center such as tmall, taobao, or retail‑connect.

Use Case : describes interactions, e.g., order payment.

Scenario : concrete instances of a use case, such as "use Alipay balance" or "use credit line".

4 Modeling Business Identity from a Value‑Stream Perspective

Modeling focuses on four coarse‑grained dimensions that together uniquely identify a transaction:

Customer Group : who uses the product (strategic client, core supplier, etc.).

Channel : the delivery medium (APP, WeChat mini‑program, external platform, etc.).

Service Mode : how the service is exposed (API, embedded H5 page, etc.).

Product : the business domain, use case, and scenario hierarchy.

By combining these dimensions (who, where, how, and what), a platform can generate a globally unique business identity that drives routing, configuration, and monitoring.

The main difficulty in business‑identity modeling lies in selecting the right elements; the technical complexity is modest, but deep business understanding is essential.