Our application requires that we keep a massive immutable ledger of past financial states (in billions of rows). For example, consider a customer’s current balance together with the history of all transactions that led to her current balance. Or a history of customer repayments towards a debt. Or a report of users who were “in debt” during a historical time window.
This type of queries are fairly common for us and not terribly difficult in RDBMS (MySQL is our current DB engine). I’m asking about Dgraph specifically because it address nicely other issues that we run into with MySQL. We would rather not replace one set of problems with another should we attempt to migrate from the RDBMS to a graph DB.
Any feedback re. graph DB or Dgraph specifically to model financial data would be greatly appreciated.
Also We have lot’s of tests with financial logic like Jepsen bank test.
Dgraph can handle the massive majority of activities that exist today in Startups. Like Fintechs and etc. If you have any specific question, I’m here.
Hi again @MichelDiz, what’s the largest integer that can be stored in Dgraph? We may have Indonesian customers and the Rupiah might potentially need us to store amounts up to 2 trillion. I tried searching for range limits for types but couldn’t find any info. Thanks!
That I’m not sure, but I’ll check it and get back to you.
BTW, not sure if you are friend or colleague of Slisznia, But it is not recommended to ask questions in old topics. Because it triggers emails for everyone involved. And not everyone likes to receive emails unrelated to their question.