4 ms·
> The only thing relevant here is that blockchain data is almost exclusively append-only and so you can build something neater because you've got guarantees tha
by com2kid 4y ago
> The only thing relevant here is that blockchain data is almost exclusively append-only and so you can build something neater because you've got guarantees that many other problems don't have.
Append only databases have been around for decades.
Heck Kafka is an obscenely popular example today.
I've talked to people working in fields with legally mandated immutable databases, again decades old technology. In the most extreme cases the immutability is enforced using technology, such as a storage medium that only supports writing and not deleting or changing data once it has been written.
Distributed append only databases based on not trusting the people you are doing business with, and where writes cost small fortune, sure, that is new.
But the # times I want to make large transactions where:
1. I don't trust the other party
2. I can't use one of the insanely well trusted escrow agencies, some of whom have been around for literally hundreds of years and have built up trust accordingly
3. I am OK with the transaction not being reversible through the typical legal system remedies
is miniscule.
The idea of a distributed ownership ledger is more interesting, but again, if you have any level of trust with your partners, it is cheaper to throw away the entire proof of X system and replace it with a regular append only database.
That said, the provided service may very well be a better way to access existing web3 services.
> FWIW I'm consulting in this space currently, specifically dealing with blockchain data itself and it makes perfect sense to me.
Have you found any uses for blockchain that are not better served, or cannot be served, by traditional solutions?
- IanCal 4y agoI think you're arguing around something very different to what I'm saying. None of this is to do with whether web3 stuff is a good idea, or whether the underlying Blockchain setup/concept is useful or whether distributed whatevers are good. This is a product launch giving access to that data under a common API.
- com2kid 4y agoI agree that the product itself seems like a nicer way to access web3 stuff! And I'd actually be interested in some blog posts about how the authors got such dramatic speedups.
- dmitriid 4y ago> And I'd actually be interested in some blog posts about how the authors got such dramatic speedups. You did mention Kafka. They got the speed ups exactly how you get views from Kafka: dump them into a PostgreSQL, have an ElasticSearch on top. The entire throughput of the most popular chains is ~20-50 transactions per second. You can probably handle this immense load at scale that "no traditional system is suited for" on a free tier of any cloud hosting provider.