Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Attendees

Meelis Zujev (Deactivated) Taylor Downs Aleksander Reitsakas Paweł Gesek Wes Brown David Karunda Steve ConradIngmar Vali PSRAMKUMAR Ain Aaviksoo (Deactivated) Damian Borowiecki (Deactivated) David Higgins Dominika Bieńkowska (Deactivated) Jukka Aaltonen (Deactivated) Kibuuka, Arnold Nyoman Ribeka Satyajit Suri Valeria Tafoya

Agenda

Presenter

Duration

Discussion

  • Review pending action items

 Esther Ogunjimi

 10 minutes

https://www.youtube.com/watch?v=4ASKMcdCc3g

 

TECH-278 - Getting issue details... STATUS

TECH-288 - Getting issue details... STATUS

TECH-642 - Getting issue details... STATUS

Concept of adaptor

Steve Conrad

https://www.youtube.com/watch?v=kxGWsHYITAw

Adaptor Concept

Is this model correct/sufficient?

What technology/tooling do we use? Are there multiple options?

We need to focus some time on the adaptors and how do we bring existing DPGs into compliance with the specs that we're developing.

The the key idea is that the adapters are used to provide URL and payload mapping between an existing API and Gov Stack API definitions.

In contrast, the workflow building block is used to manage more complex transactions, or where you need you know to control the rollback or commit flow of a transaction. So if we or one transaction requires calling multiple building blocks, that's where you would use something like the workflow building black and then finally the information mediator is used to transfer information securely between building blocks when you're going.

what's the tooling or technology that we would use to implement an adaptor?

A simple scenario, if you have a one building block calling another one, the first building block makes a call that goes through its adaptor, which maps the URL and payload into the GovStack format; the adaptor then sends it over the wire to the adaptor and the second adapter maps that.

Status update

BB Leads

Valeria Tafoya Meelis Zujev (Deactivated) Dominika Bieńkowska (Deactivated) Steve Conrad

https://www.youtube.com/watch?v=U1vz__vR8hQ

Scrum standup-style (what we did this week; plans for next week; blockers/pain points and open/unresolved questions?

  • Specification 1.0 publication TECH-206 - Getting issue details... STATUS

 

  • Wave 3 BBs

    • eMarketplace BB -

 

  • USCT use case definition TECH-225 - Getting issue details... STATUS

 

  • Testing

 

  • Sandbox Team

 

  • Architecture Team

Building Blocks versioning

Damian Borowiecki (Deactivated)

https://www.youtube.com/watch?v=u_BcMXgws6Y

Proposed technical solution to the versioning of BBs

BB spec target reader- Persona

Ingmar Vali

https://www.youtube.com/watch?v=_W0bSen8Qjg

I have received feedback to make BB specification well readable for architects by removing the example screenshots.
"Screenshot are not appropriate for this section. You should just list capabilities, which can be understood by a Solution Architect, who already familiarised herself with sections 2 and 3. "
That raises a question- has it been decided who is our target reader?

Meeting recording

Action items

  •  

Decisions

  • No labels