Page History

...

• Future considerations.
  • Smaller services - 
    • For example, Coding List listing service as a separate service.
  • Concerns around ability to deploy up the tiers
    • Current requirements will prohibit how quickly services can be exposed.  
    • Concerns about tech stack upgrades across services.  Micro Services may or may not be impacted by upgrades (some or all).
  • If addressed well, we can get rid of silos and duplication.  
  • Resources are a concern,
    • Containers, JETTY, and how to balance. 
  • Security
    
    • Scanning will take nearly as long as the large service.
  • Instead of re-architecting all, focus on new and additional functionality (along side existing LexEVS)
  • No longer would need clients to include jars, dependencies.
  • 
    
    

Decision Points:

• Investigate services architecture to support new and additional functionality.

...

Attendees:

Discussion Points:

Strategic direction - RESTful services

• Moving to micro architecture in new areas in functionality for LexEVS
• Integrated REST services across LexEVS, Triple Store, Clinical Trials (Integrated REST Services)
• Future MDR redesign effort - areas of service support of terminologies. 
• Future CTRP support

Decision Points: