Use Cases

Sevant (Fuse) service registry powered use cases

These capabilities use a structured DDCL service registry to help teams discover APIs, map dependencies through clusters, manage specifications, and enforce naming compliance. Together they streamline integration and keep your API ecosystem consistent and well organized.

Structured Registry Search

Actor: Developer / Product Owner
Goal: Find APIs relevant to a business function using DDCL naming fields
Trigger: A developer needs to identify APIs that interact with external systems for a specific domain
Preconditions: The service registry uses the structured naming convention

Main Success Scenario

User searches by DDCL fields (e.g., Outer Domain, Context, Function)
Registry maps query terms to naming convention fields
Matching services and metadata are returned

Dependency & Relationship Mapping

Actor: Solution Architect / DevOps
Goal: Understand the downstream impact of a proposed API change
Trigger: An API is flagged for deprecation or modification
Preconditions: API relationships and clusters are maintained in the registry

Main Success Scenario

Registry surfaces related services based on Subdomain, System, and Context
Related and downstream services are listed for review
Report is shared with stakeholders before the change is made

API Specification Management

Actor: API Developer
Goal: Register, update, and organize API specifications in the registry
Trigger: New API is registered or updated
Preconditions: Naming convention metadata is available

Main Success Scenario

Developer registers or updates an API specification with DDCL metadata
Specification is versioned and organized in the registry
Teams can discover and reference the documented API

Governance Compliance Validation

Actor: Enterprise Architect
Goal: Ensure all APIs follow company naming and design standards
Trigger: A new API is registered or modified
Preconditions: API definitions and naming rules are stored

Main Success Scenario

Registry checks API metadata against naming conventions
Flags naming violations or role-context mismatches
Compliance report is generated and shared

Discover Related APIs via Clusters

Actor: Partner Developer / System Integrator
Goal: Find related APIs for integration using clusters and DDCL context
Trigger: A partner wants to integrate with internal systems
Preconditions: API clusters and domain context are available in the registry

Main Success Scenario

User browses APIs grouped by Outer Domain and Request Context
Registry surfaces related services from clusters and relationships
Partner selects relevant APIs for integration planning