Updated architecture diagram #1499
Conversation
github-actions
bot
added
the
documentation
coilysiren
requested review from
sumiat,
widal001,
andycochran,
acouch and
SammySteiner
as code owners
documentation/architecture/README.md
Outdated
| subgraph public-subnet1 [Public Subnet] | ||
| ALB["Application Load Balancer (ALB)"]:::lb --> AZ1 & AZ2 | ||
| end | ||
|  |
There was a problem hiding this comment.
(question): Is Route 53 involved in the DNS resolution if we aren't using it as a service?
There was a problem hiding this comment.
Oh, good catch!
It might be used "under the hood" by the load balancers, but we aren't using it directly. Will remove 👍
There was a problem hiding this comment.
@coilysiren (nit) we aren't using New Relic yet, so should note that in the diagram or description.
There was a problem hiding this comment.
Adding this:
This New Relic integration is shown here in a future facing capacity. Which is to say that, at time of writing, we have not started integrating with New Relic yet.
There was a problem hiding this comment.
Just for correctness, I'll add a version of the diagram to this readme that doesn't have new relic.
Summary
Fixes #1276
Time to review: 5 mins
Changes proposed
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.