Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: 0xFast – Faster Web3 APIs

0xfast.com

Post reply on HN
Print view View original

21–30 of 71 posts

Re: Show HN: 0xFast – Faster Web3 APIs

#21

Post by dmitriid »

> The solution to this problem becomes more complex with scale. Distributed transactions, sharding, replication, and fault tolerance are notoriously slow.

And yet, suprisingly (not) they power everything at scale unimaginable to anything happening in crypto. The "amazing scalable crypto" barely manages the complexity and scale you can easily run from a Raspberry Pi with a sqlite database.

> We built a cheaper and simpler storage and indexing system from scratch that can scale to the heaviest blockchain workloads out there

Translation: you are dumping blockchain data into traditional databases running on traditional servers and backed up by a traditional Elastic Search.

Re: Show HN: 0xFast – Faster Web3 APIs

#22

Post by CharlesW »

IanCal wrote: post #8
FeistySkink wrote: post #5

The main page and the description is in a strange meme format, that creates a strawman Web2 Databases (cringe) and then argues that Web3 (but what is it?) is better without any concrete arguments. Is Web3 (or is it web3?) just a new way of saying web-scale, but now with blockchain? Edit: I feel like we need somebody like Coffeezilla to unwind the web3 mystery in a digestible format for the rest of the tech world.

It's not arguing about the difference between web2 and web3. It's arguing two main things 1. Web3 data is different from what most classic databases are optimised for, because of how it's accessed and the (mostly) immutable guarantees. 2. This service is better than other web3 api providers. FWIW I'm consulting in this space currently, specifically dealing with blockchain data itself and it makes perfect sense to me.…

> Web3 data is different from what most classic databases are optimised for, because of how it's accessed and the (mostly) immutable guarantees.

Nah. Blockchains are (of course?) not the first database use case where immutability is necessary. Blockchains aren't unique in terms of access patterns, either.

Re: Show HN: 0xFast – Faster Web3 APIs

#23

Post by Geee »

FeistySkink wrote: post #5

The main page and the description is in a strange meme format, that creates a strawman Web2 Databases (cringe) and then argues that Web3 (but what is it?) is better without any concrete arguments. Is Web3 (or is it web3?) just a new way of saying web-scale, but now with blockchain? Edit: I feel like we need somebody like Coffeezilla to unwind the web3 mystery in a digestible format for the rest of the tech world.

Web3 is decentralized web, like web 1.0 - but with tokens this time! Tokens solve the issue because you can buy and hold them and get rich! Buy my shitcoin!

Seriously web3 is just another way to create hype for arbitrary crypto tokens and Ethereum. In a few years there will be something else - quantum web or something to suck new buyers in.

Re: Show HN: 0xFast – Faster Web3 APIs

#24

Post by CharlesW »

dmitriid wrote: post #21

> The solution to this problem becomes more complex with scale. Distributed transactions, sharding, replication, and fault tolerance are notoriously slow. And yet, suprisingly (not) they power everything at scale unimaginable to anything happening in crypto. The "amazing scalable crypto" barely manages the complexity and scale you can easily run from a Raspberry Pi with a sqlite database. > We built a cheaper and sim…

> Translation: you are dumping blockchain data into traditional databases running on traditional servers and backed up by a traditional Elastic Search.

It's ironic that the solution to blockchain problems is so often re-centralization.

Re: Show HN: 0xFast – Faster Web3 APIs

#25

Post by splix »

It doesn't seem that it's the correct metrics, none of them makes much sense.

Something is definitely wrong with the "Queries per second", it doesn't look like something significant. My usual load for a single node is about 300 req/sec. That's just an average number. Sometimes I do up to 10K req/seq. That consumes some noticeable amount of CPU, but nothing special and the bottleneck seems to be not here.

And I think the main issue is the "Latency" chart. Because my average latency is about 3.5ms. It's like 10x faster. They cannot be so slow.

So I guess the real problem is that the author measures the network. Not the service. So a link to Alchemy happens to be slower than a link to his own server. And the network is the main bottleneck in both cases, because you can easily do 10x of those numbers with a good network.

Re: Show HN: 0xFast – Faster Web3 APIs

#26

Post by egorfine »

I have played around. I love it! At 23gate.com we are not yet running our nodes for chainId=0x01, so I would love to switch our downloader to 0xfast.

However it seems that there are minor incompatibilities between 0xfast and generic RPC so it fails with ethers.js one getTransactionReceipt. I will look into it in the coming days and get back to you.

Post reply on HN