[Platform Arch]: Lighthouse/VSP

[aparcel-va]

Topic

Lighthouse/VSP overlap/separation

Summary

Presently, Lighthouse and VSP are intertwined. Both teams contribute code to vets-api, share the dsvagovcloud AWS account, and utilize the api.va.gov domain name. As Lighthouse pivots from the VSP-hosted Kong API gateway to Google's Apigee platform, it'd be worth re-visiting the "Lighthouse + VSP shared responsibilities" document and working towards solutions that remove impediments from the Apigee migration.

Status

Ready

Documentation

• Lighthouse + VSP shared responsibilities.pdf
• https://vfs.atlassian.net/wiki/spaces/ECP/pages/1907523684/Explainer+-+VA.gov-Lighthouse+Overlap

Points of Contact

@aparcel-va

Topic

• [ ] Frontend application
• [X] Backend application
• [X] Network
• [X] Other

Other:

Lighthouse/VSP separation

[f1337]

Following-up on our working group review: Is there anything else you need from Platform @aparcel-va?

[f1337]

@mchelen-gov Is there anything from the follow-up DSVA Slack convo that we need to create tickets for?