3 ms·
> One one company maintains it, so the others are relying on that company to keep it up. This isn't easy. If that database goes down for some reason the other c
by viraptor 9y ago
> One one company maintains it, so the others are relying on that company to keep it up. This isn't easy. If that database goes down for some reason the other companies can only wait while the database is fixed.
Or you could use a system with a well designed replication mechanism and designed to work offline. For example http://couchdb.apache.org/ http://couchdb.apache.org/ should provide the same functionality you're after. If you have multiple entities that don't trust each other 100%, you can structure the data to be essentially an event log and filter the replication to reject modification/deletion.
- foepys 9y agoPlus with CouchDB (or similar) you don't have the fear of somebody racking up more mining power to conduct a 51% attack.