{"page":"/blog/identity-graph-architecture","modified":"2026-11-10","license":"https://creativecommons.org/licenses/by/4.0/","columns":["Layer","Option","Good for","Watch out for"],"rows":[["Edge store (system of record)","Relational or lakehouse table of edges, partitioned by date","Audit, deletion, recomputation","Needs a batch job to build clusters"],["Cluster build","Connected components in Spark or SQL; or a managed service","Nightly or hourly rebuilds","Giant components from shared IPs or shared emails"],["Graph database","Property graph store","Exploring paths, debugging merges","Not needed on the bid path"],["Serving store","Key-value lookup from node to person ID and partner IDs","Real-time enrichment","Must expire and delete in step with the edge store"],["Managed resolution","AWS Entity Resolution, with up to 20 data inputs per workflow","Teams without a matching team","Data and rules sit inside the provider's service (AWS user guide)"]],"sourceUrls":[[],[],[],[],["https://docs.aws.amazon.com/entityresolution/latest/userguide/what-is-service.html"]]}