Open APIs

Hello everyone.

Currently, we have an API that returns all assets associated with a client, whether products, services, or resources.
For the TMF implementation, we selected TMF637, TMF638, and TMF639 for each asset type.
So, when the consumer needs to query about the three asset types, the flow begins with 637 (Parent Product), but must perform a query for each Child Product to obtain references to 638 (Services), 639 (Resources), and 637 (Child Products) associated with the Parent Product (ProductId/PO).

Is there a TMF that performs this orchestration between the different resources? Or should we implement an ODA component?

We greatly appreciate your help.
Best regards,
Soledad.

------------------------------
María soledad Alfonso
Entel Chile
------------------------------

hi,

This should not be an ODA component. You could use:

• API gateways
  
• Backend-for-Frontend (BFF) layers
• Middleware platforms
• orchestrators

we use an open-source lightweight orchestration layer (you can ask the name by private message if you wish). It can do:

• Transform data from multiple sources,
  
• Enrich data combining results, or injecting computed fields,
• Aggregate data across different domains or services...

... into a single endpoint for the consumer

for example, in the Engagement Management domain, we use the above capability to serve data to employee and customer engagement channels (app, web). the component orchestrate several TMF APIs:

• Product inventory + billing info+ product offering Qualification + Recommendation
• Product configurator + product offering Qualification
• product offering Qualification + Recommendation

you can create any endpoint with any data you need.

------------------------------
Kind regards,

Matthieu Hattab
Digital Sales Domain Architect
Lyse Tele AS
------------------------------