|
|
|
|
|
by kilburn
2722 days ago
|
|
You are getting downvoted because of your attitude. Even if your GUN database is really that awesome, here are some points for you to reflect on: - What is "easy" for you might not be for others. - Banking systems don't use strong consistency. They can just rollback/swallow the costs of invalid transactions after the fact. Online mom-and-pop shop... maybe they can, maybe its better for the site to just have some downtime sporadically and avoid such hassles entirely. - P2P is a nightmare for anything that requires audit trails (and there are legal requirements about that in many industries). - There exists a whole ecosystem of databases dedicated to analytical processing workloads (OLAP). Graph databases are typically not the best at it. - Conflicts happen. Your "conflict-free" datatypes embed the conflict resolution rules in the data structure. This is fine for some conflict resolution rulesets, but it cannot be done for some other sets (e.g.: in these weird circumstances, the user decides what the resolution is by clicking a button). |
|