-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Task]: Update Architecture Diagram #1276
Labels
project: grants.gov
Grants.gov Modernization tickets
Comments
1 task
I definitely want to do this in LucidChart. Mermaid becomes unwieldy and frankly kind of ugly when used for an AWS infrastructure diagram |
platform has an architecture diagram that can be used as a baseline: https://github.com/navapbc/template-infra/blob/main/docs/system-architecture.md |
Working on this now |
FYI - these images are best viewed via downloading them first. That way you can zoom in, etc etc |
coilysiren
added a commit
that referenced
this issue
Mar 20, 2024
## Summary Fixes #1276 ### Time to review: __5 mins__ ## Changes proposed - removes the mermaid AWS architecture diagrams - adds a lucidchart AWS architecture diagram ## Additional information This architecture diagram is meant to be viewed as an abstraction of the important high level components of our architecture. As such, there's some fine details that are intentionally missing from it. For example, the "VPC Endpoints" section intentionally doesn't list every single AWS service we are accessing through VPC endpoints. Given that, I'm interested in feedback on whether or not the architecture diagram is missing some high level components. For example, in early versions of this diagram I forgot the foreign data wrapper + step functions setup. Large components like that are important to have called out in the diagram, so please let me know if any are missing! ~Also note that this diagram pre-emptively includes New Relic.~
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
The current architecture diagram is out of date (does not include database replication, contains a-z failover, among other issues). This task is to update it.
The original diagram was created in mermaid. The Nava template has a lucid template that we may want to use moving forward. A diagram in lucid can better represent the architecture and easier to update as things get more complicated, though we can discuss as a group.
Acceptance criteria
The text was updated successfully, but these errors were encountered: