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.