2023-03-24 Sandbox back-end tech meeting

Owned by Heidi Kuum (Deactivated)
Last updated: Mar 28, 2023
2 min read

 Date

Mar 24, 2023

 Participants

  • @Bert Viikmäe (Deactivated)

  • @Tsvetomir Krumov

  • @Vladislav Todorov

  • @Akseli Karvinen

  • @jarkkohyoty

  • @Heidi Kuum (Deactivated)

  • @Meelis Zujev (Deactivated)

 Goals

  • How to proceed with sandbox developments

    • Sandbox API development

    • Adapters

    • Sandbox Portal

 Discussion topics

API developments:

Non of current BB are currently compliant with GovStack API specifications. These BB providers, who have signed the contracts will just start developing their API endpoints. We assume that probably within three months there will be some kind of first results by them, and probably they will discover issues, that will change initial API specs. Also, the GovStack API specifications aren't finalized (currently fe. Registration BB API specs are work in progress).

As there are currently no compliant BB and we cannot use them as needed to run the MVP flow. Only way would be to do custom development, but as already discussed with Wes and Satyajit, it is not what is expected from us and this way the APIs would not be reusable by other BB.

Therefore we see that it is not efficient nor useful to proceed with sandbox side API development currently and put this on hold.

What we can do:

  • Do the sandbox MVP, install the current BB candidates and connect with x-road

  • Write specifications on

    • how to install the BB to the sandbox

    • how to integrate with x-road

Sandbox portal:

Can we do something with it currently?

Sandbox portal is a gateway between APIs and frontend. As we don't have any actual APIs we cannot proceed with this because this would be at this point mostly hypothetical.
Potential ways forward that would be beneficial for the Govstack community-
?Continue creating “mock” API-s to support Demo flow live implementation in future. Wait till 1st release of involved BB-s will provide API-s compliant with the specification. Continue work toward 1 st country engagement Use Case by adapting Use case with existing API-s.

Adapters:

GovStack non-functional requirements say, that adapter is used to “translate” the API, provided by the application (BB) into a format that is consistent with BB specifications in GovStack.

As the application is owned by the BB provider and the application APIs are known to BB providers, therefore the “translation” should be done by the BB provider.

Creating sandbox-specific adaptors seems very challenging and questionable because thus adaptors wouldn't be reusable for new Use case roll-outs.

 Action items

 Decisions

  • Put USCT MVP flow technical developments (sandbox APIs) to hold, until some of the BB candidates is compliant with GovStack specifications

  • Continue with the topics we can do in current situation (described above)