[BE] 10-10EZ - Event Bus: Discovery on Event Bus integration

[hdjustice]

Benefit to the Veteran

By onboarding to the Enterprise Event Bus, we will be able to produce submission events, as well as consume any events that communicate the status of the submitted application (consumption is future state). Other applications and/or systems will be able to consume the submission event and use that status for their needs without direct connection or integration with 10-10EZ.

Background

Info shared from Patrick:

next up: had a call with other folks in VES (the office, not the enrollment system) about their work creating an enterprise customer transaction tracing systems (aka the enterprise event bus). basically a central point where systems report in changes in status for transactions. so for 1010ez (or cg for that matter) va.gov would notify the event bus whenever a user submits an application. and then enrollment system would notify event bus when it is received, and then again when it gets to the next phase of processing, and so on through completion. systems could subscribe to event bus topics (e.g., “1010EZ events”) and build logic off changing transaction status (e.g. notifications). in addition, all event data will be dumped into a big analytics database so we can collectively identify choke points / issues / gaps between systems.

there is interest in 1010EZ events being the first type of transaction traced in the system.

what this means for us: at some point, probably this summer, we’ll need to integrate with the event bus to send 1010ez submission events. this should be relatively low lift as I'm told the vets-api <<-->> event bus system integration is being done by another team, so we’d just leverage that.

This ticket is to determine the process to onboard to Event Bus as a producer of submission events.

Resources

• Event Bus Developer Portal
  • Enterprise Event Bus - Diagram
  • Events flow through the Event Bus - Diagram
  • Steps to become a Consumer of Events
  • Steps to become a Producer of Events
  • Event Catalog on CODE VA - MUST be on the VA Network to access)
• Slack channel & team info
  • #ves-event-bus
  • Karen Taylor - PM
  • Alan Werner - PM
  • Emily Wilson - Engineer
  • Notes from our first meeting

Tasks

• [ ] Initiate conversation with Event Bus team around becoming a producer of events on Event Bus
  • They are aware of our team and will have prepared for us to start this discussion. If you would like a intermediary to assist, check with our Emily.
  • Also, include Patrick Bateman in all conversations (slack, meetings, etc)
• [ ] Schedule/attend meetings, as needed, to discuss integrating with Event Bus as a producer (sending our Submission events and possibly other events, tho I dont know what they would be) and steps to take
  • All teammates can be included on this meeting
• [ ] Outline process steps within this ticket for future reference
• [ ] Create/Update technical documentation (workflow diagram, etc) to include the new API(s) information
• [ ] Review steps with team to create next-step tickets

Acceptance Criteria

• We know what onboarding steps to take to onboard as a producer of an event to the Event Bus

[hdjustice]

Call scheduled for 7/15/2024

[hdjustice]

Placing ticket in icebox for now Received this note from Patrick Vinograd via DSVA slack.

All concerned, Due to a contract protest, the Enterprise Event Bus will experience a gap in vendor support starting August 11. Exact date when support will resume is unknown but best estimate is around October 31. During this time, VA FTEs will be providing best-effort support for lower environment integrations that are underway. But we will not be promoting any partner integrations to production or up through any additional environments that are not already established. As we learn more and clearer timelines develop, we will make sure to share that information. For any additional questions please contact Anthony Nguyen and/or Patrick Vinograd.