Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Date

ZOOM Meeting Information:

Monday, October 3rd at  9am PT/12pm ET


Join Zoom Meeting

https://zoom.us/j/7904999331

Meeting ID: 790 499 9331

Attendees:

  • Sean Bohan (openIDL)


Agenda

Drawings here: https://lucid.app/lucidchart/ac20d4e1-50ad-4367-b5cf-247ed9bad667/edit?viewport_loc=-301%2C-37%2C3200%2C1833%2CkgLSxXlpoGmM&invitationId=inv_de1a5e61-8edc-488a-90ee-8312f8c69cd4#

  1. Continue discussion - Architecture& Scenarios
    1. openIDL - Architecture Definition Workspace (NEW)
  2. Previous Discussions 
    1. openIDL - System Requirements Table
    2. openIDL - Policies
    3. openIDL - Operating Roles

Notes:

  • Notes included in Architecture Discovery Document
  • Notes from 9/26-9/27 Meetings:

    • Technology Stack:

      • Hyperledger Fabric
      • Kubernetes
      • NodeJS / Angular
      • AWS

      Tenets:
      • Must Pass security standards of all carriers
      • Must meet data privacy expectations of all carriers
      • Cost of running the node is agreeable / reasonable / commensurate with function

      Technical Directions:
      • Ingestion format is the stat plan
      • HDS will be a relational database (business users need to use SQL, Mongo is a non-starter)
      • Standard, lowest common denominator SQL
      • Denormalized and keep the tables flat
      • Stored Procedures: not currently in consideration (orchestration, reviews, security implications, "a lifelong commitment")
      • No executing code behind the trust plane
      • We need to put together a deck for the teams (Security, Engineering) at the Carriers to explain this solution


TimeItemWhoNotes




Documentation:

Notes: (Notes taken live in Requirements document)

Recording: 







  • No labels