Attendees
Paweł Gesek
Taylor Downs
Jukka Aaltonen (Deactivated)
Uwe Wahser
Oleksii Danyliuk
Steve Conrad
Apologies
Wes Brown
Agenda | Presenter | Duration | Discussion |
Review Process | Wes Brown Steve Conrad | 20 minutes | Go Arch team to go through each BB and do a manual review. Known/outstanding issues: Review tasks are assigned here: Jira Legacy |
---|
server | System JIRA |
---|
serverId | f5c6bdaf-d23e-347d-a1e8-579e20a81dda |
---|
key | TECH-394 |
---|
|
Jira Legacy |
---|
server | System JIRA |
---|
serverId | f5c6bdaf-d23e-347d-a1e8-579e20a81dda |
---|
key | TECH-393 |
---|
|
All comments to be logged here: Architecture Team Review Determine next steps and schedule for review work. |
Adaptor Conversation | Steve Conrad PSRAMKUMAR | 30 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? An application making a request of a GovStack BB needs to know how to format that request in the correct format For a BB like registration, can we make a requirement that an outbound request has to have a specific format? Taylor: this is outside the scope of the current understanding of GovStack Pawel: outbound adaptors add complexity Uwe: what is the ‘man in the middle’ and how would it work? Pawel: this could function like an ESB If there are scenarios where one BB communicates directly with another, what is the architecture?
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?
|
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? |
...