Practice English vocabulary for serving knowledge graphs: graph APIs, query latency, indexing for traversal, read replicas, and sharding by domain.
0 / 5 completed
1 / 5
What does 'the graph API serves entity lookups' mean?
A graph API provides an abstraction over the underlying graph database. Clients send entity lookup requests (e.g., 'get company entity by ID', 'get all products related to this category') and receive structured responses without needing to write graph query language themselves.
2 / 5
What does 'the graph query responds in 15ms at P99' mean?
P99 latency is a critical serving metric. A P99 of 15ms means the graph handles the vast majority of queries quickly. Tracking P99 rather than average exposes tail latency that affects real users — a slow P99 creates a poor experience for 1% of requests, which at scale means thousands of users.
3 / 5
What does 'the graph is indexed for fast traversal' mean?
Graph traversal performance depends heavily on indexes. Without indexes, finding 'all transactions connected to this account within 2 hops' requires scanning all nodes. With proper indexes on relationship types and property values, the database jumps directly to relevant starting points.
4 / 5
What is 'a read replica that serves query traffic'?
Graph databases under heavy query load can be scaled by adding read replicas. All application queries are directed to replicas; writes and ingestion go to the primary. Replicas receive replication stream updates from the primary to stay current.
5 / 5
What does 'the graph is sharded by domain' mean?
Domain sharding separates graph data by business domain into independent deployments. The product knowledge graph, the identity graph, and the fraud detection graph can all scale and evolve independently. Cross-domain queries join across shard APIs rather than requiring a single massive graph.