Skip to content

Confusing Statement that Platform Mesh Services should expose ORD #6

@valentinvieriu

Description

@valentinvieriu

A confusing statement regarding the services that are part of the Service Marketplace can be found in the document titled "service_supplier.md."

Service Supplier
Role: Publishes services with aligned metadata, ensuring discoverability, traceability, and easy consumption by others.

As outlines in the sections Services and Service Management and Platform Mesh: Service Supplier Perspective, a service in its most general form is a solution or active entity, which offers some API to its consumer. To make a service available, the supplier must register a service provider, which manages one or more services, in a service marketplace. The registration should include all necessary information for potential consumers, including API definitions. Open Resource Discovery facilitates consistent interface modeling across distributed systems, enabling standardized service description, discoverability, and streamlined integration within complex architectures.

Currently, our implementation of PlatformMesh Services does not utilize ORD, and there are no quality gates in place to ensure that "the registration includes all necessary information for potential consumers, including API definitions."

Expected Behavior: The reader should be clear about ORD's role and how PlatformMesh utilizes or does not utilize ORD functionality.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions