VRO Architecture Diagram
VRO runs in Docker containers on Kubernetes clusters hosted on AWS infrastructure in the VA Enterprise Cloud (VAEC). Deployments are configured in ArgoCD and executed through the Lighthouse Delivery Infrastructure (LHDI).
VRO comprises 1) apps for platform functionality and 2) apps built by partner teams (leveraging the platform functionality). The VRO team maintains the platform functionality, including the mechanisms for running continuous integration (CI) tests and deployments of apps built by partner teams. Partner teams maintain the source code of their respective apps. VRO is designed to support multiple apps across multiple partner teams.
The VRO platform functionality includes data services that allow partner teams using VRO to access other VA systems, such as the Benefits Gateway Service (BGS) and Benefits Integration Platform (BIP). By design, this removes the burden on partner teams of individually negotiating and maintaining access to those VA systems and allows VRO to create efficiencies. The VRO data services are exposed to partner team apps through a RabbitMQ message queuing protocol (VRO RabbitMQ Strategy).
The VRO Architecture is diagrammed in this Mural from the perspective of a single production-level environment, and is duplicated in each of our deployment environments. It is a living document, and will be updated to reflect changes made to the architecture over time.
Below is a copy dated 10/22/2024:
- Link to Mural
- Zoomable Image
- App/Service managed by a VRO Partner Team
- App/Service managed by VA and external to VRO
- Lighthouse APIs
- BIP APIs
- BIE Kafka Event Stream
- BGS API
# TODO, did we want to add a link here?