Skip to content

GBPA PARTNER

TigerGraph: graph database for complex relationships

Graph database for complex relationships

TigerGraph

TigerGraph is a graph database built to query, at high volume, the relationships between people, accounts, transactions, systems and processes.

GBPA uses it when the answer lies in the connections — dependencies between systems, network fraud, a single customer view — and a relational table can't cope.

When it makes sense

TigerGraph suits cases where the answer lies in the connections, not in the rows of a table: network fraud, a single customer view across many sources, and dependencies between systems and processes.

What it delivers

  • Multi-hop relationship queries with high-volume performance.
  • Detection of network patterns such as fraud and collusion.
  • A map of dependencies between systems and processes.
  • A unified customer view from multiple sources.

Where we apply it

Fraud detection

Network patterns, such as collusion and linked accounts, identified across several layers of relationships.

Single customer view

Data from many sources unified around each customer.

Dependency map

Which systems and processes depend on which, before a migration or automation.

FAQ

Frequently asked questions

What is a graph database?

It is a database that stores entities and the relationships between them as its main structure. Queries such as 'who is connected to whom, in how many hops' stay fast even at high volume.

When should you use TigerGraph instead of a relational database?

When the query crosses several layers of relationships, as in network fraud. In a relational database this requires many joins and loses performance as volume grows.

What does GBPA do in a TigerGraph project?

We model the graph from the data sources, build the queries for the business problem and integrate the results into processes and systems.

Shall we look at your operation?

The maturity assessment reads your processes and shows where automation and AI pay back first.