3 great graph database blog entries around the subject of fraud from the team at +Neo4j - the World's Leading Graph Database -
First party bank fraud - linking people via addresses, phone numbers, accounts is just not possible in a standard hierarchical database. I've seen for myself the duplicates that can exist in a data warehouse when you load all your order management data. The different spellings, the duplicate addresses, etc. Bringing it all back to the one address, as an example) can be a major undertaking.
Insurance fraud - how a graph database can be used to map out the relationships between people and claims - I believe this can be done much earlier in the process now using a graph database as opposed to waiting for complicated analytics.
E-commerce fraud - how a graph database can be used efficiently to detect fraud - something that in the past has been rather slow and clunky.
No comments:
Post a Comment
Note: only a member of this blog may post a comment.