3 ms·
This is a blogpost intended to demonstrate the usefulness of applying neo4j to a specific problem. All the challenges you cite are valid, but they do not negate
by chatmasta 11y ago
This is a blogpost intended to demonstrate the usefulness of applying neo4j to a specific problem. All the challenges you cite are valid, but they do not negate the value of using neo4j in this scenario.
You can solve these problems by adding to the list of identifiers. Off the top of my head: browser fingerprinting, request latency, IP subnets, IP ASNs, hsts super cookies...
Stopping fraud is always going to be a cat and mouse game. The goal is not to eliminate fraud completely, but to make it so difficult for fraudsters to use your service successfully, that they would rather move to the next target. If a fraudster is specifically targeting your service, they will get around any blockades you put in front of them. But you can still make it as hard as possible to circumvent those blockades.
If you deter a high enough percentage of fraudsters, you mitigate your risk of chargebacks. That risk will never be zero. But you should certainly do all you can to minimize it.
- ryanlol 11y agoMy main point was that despite what the article implies, these techniques are far from new.
- happywolf 11y agoBut the tone of the blog post implies this graph thingie is _the_ solution: "How graph databases stop fraud e-commerce frauds in real-time" - note the use of 'stop' and 'real-time'. "Fortunately, graph database technology is able to detect the patterns that arise around these e-commerce fraud scenarios and put an end to them in real time" Again, look at the terms used: 'put an end' and 'real time'. I am not trying to nit-pick, but what has been discussed is far from being able to put an end to fraudsters. Maybe this could weed out some of the newbie frausters, but that is it. Disclaimer: I work in the payments industry.