Live data from Hacker News

AutoDapp: a proposal to decentralize existing web apps

raymondcheng.net

1–10 of 47 posts

Re: AutoDapp: a proposal to decentralize existing web apps

#3
So I'm not familiar with the dapp apps internals like the ones described in the article. Does anyone have a quick summary of: How do you do user authentication and other "secret data" cases if the data is visible to everyone? Let's say there's an app with user-configurable webhooks which need to be used by the server, but shouldn't be announced to everyone.

Re: AutoDapp: a proposal to decentralize existing web apps

#4
Trying to understand this one - this is saying we take an standard 3-tier app and instead of storing data in our normal sql/nosql database, we route it through some kind proxy called a "validator", which is a blockchain based data store, that uses the same database API.

And the benefit of doing this is to allow other users to be able to validate the integrity of data and ensure historical changes cannot be overwritten?

So who pays for the transaction storage costs? and how does this validator thing work?

Re: AutoDapp: a proposal to decentralize existing web apps

#7
So, it's not even that the SQL state is distributed, it's that every change to the SQL state has to be "validated" and appended to a blockchain? At a 1M DAU traffic level?

How often are blocks/writes written? Who pays for all that data storage? How "decentralized" would it really be, considering the incredibly onerous requirements to run a validator at the target scale?

Re: AutoDapp: a proposal to decentralize existing web apps

#8
Hrm.. interesting idea!

The tl:dr; appears to be "we built a blockchain based query logger" where essentially the consensus appears to just be that it is valid SQL, and defines an ordering of the statements. Then once everyone agrees to apply the change, then it is applied... With (AFAICT) no interaction with the DB during the consensus process?

This seems to be a bit naive of features like locks and transactions that are critical to most DBs, so while maybe you can define a global ordering of statements, the execution of those statements may be nonsensical and result in a lot of failed transactions. For example, it seems like you could grind the usability of the system to a halt by flooding the validators with 'valid' SQL designed to create as many conflicts as possible that would cause a ton of writes to fail to commit.

I agree with the desire for more services to become decentralized, and this is a novel idea, but (IMHO) more and more the technical hurdles of blockchains often bring more challenges than they solve.

Re: AutoDapp: a proposal to decentralize existing web apps

#9
post #8

Hrm.. interesting idea! The tl:dr; appears to be "we built a blockchain based query logger" where essentially the consensus appears to just be that it is valid SQL, and defines an ordering of the statements. Then once everyone agrees to apply the change, then it is applied... With (AFAICT) no interaction with the DB during the consensus process? This seems to be a bit naive of features like locks and transactions tha…

This is naive of any real-world, large scale use of RDBMS systems. Not to mention any actually distributed storage systems.
Post reply on HN