Skip to main content

sherpa-krane

The early versions of MS Sherpa 2.0 will exists in a sort of limbo between the old MS Sherpa backend/platform and Krane. For this to work the new MS sherpa app will need to talk to the old MS sherpa backend for all functionality except the 2MWT.

Context​

  • MS sherpa 2.0 will authenticate directly with the Auth0 MS sherpa tenant

Sherpa - Krane​

The calls for the following endpoints/API in the app will need to be transform/adapted to talk with the old MS sherpa backend:

  • GET Timeline/Today Screen
  • GET Experiment results (2mwt, sdmt, questionnaires)
  • GET User information
  • POST SDMT
  • POST Questionnaire Answers
  • POST Notes (part of smdt/2mwt?)
  • ...
note

Some of these changes have already been made.

The 2MWT data cannot be sent directly to the backend for two reasons:

  1. The new 2MWT pipeline runs entirely on Krane
  2. The new 2MWT frontend streams the data to the backend using gRPC streams which are not supported by the MS sherpa backend

To solve the problem the following architecture is proposed:

  • Create a new small to consume only 2MWT data and endpoints. This service only exposes the gRPC endpoint with MS sherpa authentication (option 1). Alternatively, allow the Krane Gateway to accept MS sherpa auth tokens and hardcode the correct tenant for the gRPC endpoint (option 2).
  • Create a service in the MS sherpa cluster (2MWT Consumer) to consume 2MWT result messages.
note

All new (red) components in the architecture are temporary until a full migration to Krane has been completed.

Option 1​

Sherpa-Krane

Option 2​

Sherpa-Krane

MS Sherpa Questionnaires​

The current Sherpa questions can simply be fetched and saved in the MS Sherpa backend as usual. MS Sherpa 2.0 will also include new, much more extensive questionnaires. To properly handle this we propose a similar approach to the 2MWT test:

  • Handle new questionnaires on Krane side
    • Improve Krane questionnaire service and related questionnaire software components to support the requirements as set by MS-521
    • Improve Orikami App and MS sherpa 2.0 App frontend questionnaire handling and logic
  • Accept and handle MS Sherpa auth tokens in gateway for questionnaire endpoints.
  • Consume questionnaire answer messages on the MS sherpa backend.

Sherpa-Krane-Questionnaires