Skip to main content

Asset Compatibility Events

Summary​

There is no separate compatibility event type. Compatibility identity travels as a field (AssetCompatId) inside the six lifecycle events, preserving the monolith identifier space during the transition.

Audience​

Engineering, integration, QA, architecture, security, and product reviewers.

Reference Content​

No distinct compatibility event​

The verified source defines exactly six asset integration contracts. None is a compatibility-specific event. Compatibility is expressed as data carried in every event, not as its own event.

Compatibility identity in the payload​

FieldRole
AssetIdCanonical GUID identity
AssetCompatIdNumeric identity in the monolith AssetRecord.Id space
AssetCodeStable business key used when AssetCompatId is not yet assigned

AssetCompatId may be 0 for a record whose database key is assigned in the same transaction (for example AssetRequested at create). Consumers key on AssetCode in that case. The completeness guard intentionally does not require AssetCompatId to be positive for this reason.

Why it exists​

The compatibility identity keeps the numeric identifier aligned with the monolith so compatibility-shaped HTTP surfaces and downstream consumers can correlate an asset across the transition without a schema change on the frontend. The identity origin and generation are documented in the database section.

Transitional classification​

Because the numeric compatibility identity coexists with the canonical GUID identity, the eventing model is Transitional. Retirement of the compatibility identity and the timing of that retirement require confirmation.

Public-safety note​

Actual compatibility identifiers and asset codes are intentionally excluded.

Source References​

  • microservices/src/contracts/Events/AssetLifecycleEvents.cs
  • microservices/src/asset-service/Domain/Asset/AssetDomainEvents.cs
  • microservices/src/asset-service/Infrastructure/AssetDbContext.cs

See Also​

Keywords​

  • Compatibility identity
  • CompatId
  • Transitional

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-17
  • Review cycle: Quarterly