Agenda

Presenter

Duration

Discussion

Review Process

@Wes Brown

@Steve Conrad

 10 minutes

Arch team to go through each BB and do a manual review.

Known/outstanding issues:

• Key Digital Functionalities for IM

• There is manual duplication of data structures/API specs between the actual API documentation and other sections, which will be hard to keep in sync

• Return to comments on non-functional requirements and security in a future meeting

Review tasks are assigned here:

https://govstack-global.atlassian.net/browse/TECH-394

https://govstack-global.atlassian.net/browse/TECH-393

All comments to be logged here: Architecture Team Review

Determine next steps and schedule for review work.

Adaptor Conversation

@Steve Conrad

@PSRAMKUMAR

40 minutes

Adaptor concept: Adaptor Concept

Core questions:

• Is it valid for a BB to initiate a request to another BB? What about UX or BBs like Registration? (Talked through on April 21)

• Can an adaptor handle a complex (1:many) transaction, or do we need workflow?

• What technologies could/should be used? API Gateway, custom code, other?

• Jarkko raised comments on the complexity of having a universal adaptors - go through his notes/comments

  • Aare: Adaptors are used to support specific products adapt to BB specs. Requests are tied to specific projects/use cases. We don’t want to build ‘universal’ adaptors.

  • Jukka: Ensure we are clearly defining the scope of what adaptors do - just data mapping or something more?

  • Taylor: Adaptors should only be tied to specific APIs that have been defined

  • Taylor: Adaptors are candidate application-specific to bridge the gap between its current API and the GovStack specification

  • Outline different ‘classes’ of adaptors:

    • URL rewriting

    • Payload mapping

    • Orchestration

  • Aleksander: Adaptors are not needed for ‘native’ GovStack products

  • Taylor: There are 2 distinct uses for workflow engines - one is long-running/async processes, and one is synchronous/composition.

    • Could say that adaptors can do synchronous calls and composition, but more complex transactions need to use workflow?

    •  

Identifying/highlighting standards

@Wes Brown

10 minutes

ID BB has called out some specific standards. How should we handle/approach?

Next steps/AOB

5 minutes

What should we prioritize?

Can we spin off small groups to work through specific tasks?