High-level Architectural Blueprint #12
Replies: 1 comment 3 replies
-
Hi Dasun and everyone, That's indeed a very good suggestion. I suggest to begin a focused group discussion thread on architectural blueprint topic to identify the broader contours of the architectural blueprint. As DCI team has initially covered interoperability between SP systems and CRVS in first workstream discussion and lot of work has already been done by Mosip and G2pconnect groups in ID and payment streams, we need to align collaborate thoughts from all groups and develop a consensual approach to define a comprehensive architectural blueprint . I personally propose to use X-road as a standard data exchange layer to connect the various components in the architectural blueprint Please suggest if you have some other thoughts on this. @vvujjini @dasunhegoda @jeremi please suggest your thoughts and when we can be available for this focused group discussion |
Beta Was this translation helpful? Give feedback.
-
Hi Everyone,
I propose creating a high-level architectural blueprint that outlines the main components and interactions within our ecosystem. This would offer a broad overview (30,000 ft. view) for stakeholders, highlighting the various players and the overall scope of the ecosystem. The high-level architectural blueprint provides a clear and concise overview, ensuring all stakeholders understand the system's core components and their interrelationships.
What are your thoughts on this approach?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions