search

microsoft / industry

This repository provides holistic architecture design and reference implementation for industry cloud based on proven success of large scale deployments and at-scale adoption with customers and partners.
MIT License
259 stars 74 forks source link

Idea: Big Picture overview for telco #234

Open rcarmo opened 2 years ago

rcarmo commented 2 years ago

Feature or Idea - What?

The overview diagram at

image

Gives a good overview of how the entire MS solution stack ties together, and should probably be the hero image for industry pages (with variations for each industry).

Feature or Idea - Why?

We probably shouldn't assume first-time readers will understand how everything fits together (even Azure folk may not have a clear picture of how Power Platform ties in, for instance) - having such a "big picture" illustration to provide situational awareness will make it easier for readers to zero in on which parts of the Foundations they ware most interested in and how they relate.

Code of Conduct

amanjeetsingh commented 2 years ago

Ack - will take this on as part of Azure-PP integration. Thanks.

amanjeetsingh commented 2 years ago

We have an internal sync next week. Will update this post our discussion on where we go with this. Thanks!

amanjeetsingh commented 2 years ago

It's worth calling out a few points before we address the end to end integration between Azure and PP etc.

  1. AfO is composed of several different services and it's still being built out by engineering. We do not have full visibility of all data entities and associated data assets which will be part of AfO end-state when all its services/features have been lit-up by engineering.
  2. As a general recommendation, across all industry scenarios, we are recommending using Synapse Link/ Dataverse as a bridge for moving data between Azure and Power Platform and vice-versa. This will enable scenarios such as analytics (on Azure and PP side) and model-driven apps scenarios (on PP side). https://github.com/microsoft/industry/tree/main/foundations/data/solutions/Dataverse

As part of early thinking, we propose two integration paths between AfO (Azure) and PP.

Path 1 - Use of Power Platform directly on top of data entities/assets (list TBC) which will be part of AfO. This is a well-trodden path for enabling analytics using Power BI.

Path 2 - Use Dataverse. As part of Telco Acclerator, CDM has been extended to include telco-specific entities. Idea being that data from specific set of AfO services can be loaded into telco model hosted on Dataverse which will then enable customers to build model-driven apps on PP. Of course, the entities on AfO and the use-cases those entities drive must be identified/documented for this path to truly make sense. Having said that, Dataverse and CDM remain our approach for moving data between Azure and PP.

Once a draft is ready, we can take feedback from everyone and take this forward.

rcarmo commented 2 years ago

Hi there!

Either path works for me from an architecture standpoint - my suggestion is that we put together a high-level view that would abstract both paths (maybe even mentioning them for awareness, but providing customers with a view to what is coming) and then build out the LLD for either path in detail.

The main benefit of doing a top-down approach like this is that we can still provide an end-to-end overview (maybe even a jumping off point for already-existing advisory and documentation) and guidance - thought leadership is one of our key differentiators here, after all.

On an anecdotal note, I see great benefits being reaped from Power Platform adoption even without Dataverse - i.e., with conventional Dynamics and Azure Public tied to 3rd party SaaS, so we might even consider Path 1 as an extension of that as well...

On 23 Mar 2022, at 12:47, Amanjeet Singh @.***> wrote:

It's worth calling out a few points before we address the end to end integration between Azure and PP etc.

AfO is composed of several different services and it's still being built out by engineering. We do not have full visibility of all data entities and associated data assets which will be part of AfO end-state when all its services/features have been lit-up by engineering. As a general recommendation, across all industry scenarios, we are recommending using Synapse Link/ Dataverse as a bridge for moving data between Azure and Power Platform and vice-versa. This will enable scenarios such as analytics (on Azure and PP side) and model-driven apps scenarios (on PP side). https://github.com/microsoft/industry/tree/main/foundations/data/solutions/Dataverse https://github.com/microsoft/industry/tree/main/foundations/data/solutions/Dataverse As part of early thinking, we propose two integration paths between AfO (Azure) and PP.

Path 1 - Use of Power Platform directly on top of data entities/assets (list TBC) which will be part of AfO. This is a well-trodden path for enabling analytics using Power BI.

Path 2 - Use Dataverse. As part of Telco Acclerator, CDM has been extended to include telco-specific entities. Idea being that data from specific set of AfO services can be loaded into telco model hosted on Dataverse which will then enable customers to build model-driven apps on PP. Of course, the entities on AfO and the use-cases those entities drive must be identified/documented for this path to truly make sense. Having said that, Dataverse and CDM remain our approach for moving data between Azure and PP.

Once a draft is ready, we can take feedback from everyone and take this forward.

— Reply to this email directly, view it on GitHub https://github.com/microsoft/industry/issues/234#issuecomment-1076335973, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAC732ZQMOOA4PUXYV3GFLDVBMHELANCNFSM5PFCSG4A. You are receiving this because you authored the thread.

amanjeetsingh commented 2 years ago

Thanks @ranieuwe - agree with you. Let us get the first draft ready and we can tweak and also provide commentary on considerations; rationale behind it etc.