"We build and run our own servers. In datacenters."
Is this a selling point today? Suddenly their background in on-prem architecture, operations, security, and network management becomes very important.
41–50 of 71 posts
"We build and run our own servers. In datacenters."
Is this a selling point today? Suddenly their background in on-prem architecture, operations, security, and network management becomes very important.
Earlier quoted context omitted.
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" means nothing. If you're referring to blockchain data, say blockchain data. "Web3" doesn't lend anything to technical conversations and is best used on board rooms full of coked up investors interested in dropping money on another dumb crypto bro's vision to change the world.
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.…
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?
Earlier quoted context omitted.
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.
Earlier quoted context omitted.
"Web3 data" means nothing. If you're referring to blockchain data, say blockchain data. "Web3" doesn't lend anything to technical conversations and is best used on board rooms full of coked up investors interested in dropping money on another dumb crypto bro's vision to change the world.
The descriptions made absolute sense to me, the target audience - someone developing with these systems. You can complain about it if you want, but it's like complaining that serverless things need servers underneath - maybe technically accurate but not a helpful discussion to have.
Even so, in a technical setting I often hear engineers refers to "hosted function" or "function service" when referring to "serverless" infrastructure.
Earlier quoted context omitted.
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.…
> The only thing relevant here is that blockchain data is almost exclusively append-only So, Apache Kafka. Edit: as anyone who actually does this for a living: you never use the append-only log as your source of data. Precisely because it's very expensive to reconstruct it > so you can build something neater because you've got guarantees that many other problems don't have. So, first you have to find problems for you…
Does that give access to the full history quickly?
> Edit: as anyone who actually does this for a living: you never use the append-only log as your source of data. Precisely because it's very expensive to reconstruct it
Yeah I don't want to do that, but I do need to in order to process the data. For those that don't want to do this, and want to quickly access just the latest state, that's exactly what services like this offer.
Earlier quoted context omitted.
Guess I better stop using email too, that's infrastructure for scammers.
Name one Web3 use case. There are more use cases for email than scamming.
[0] https://www.cnbc.com/2022/03/23/ukrainian-flees-to-poland-wi...
No sure what the purpose of this really is. But the pricing seems bizzare. Hetzner cloud costs 1€ per extra TB (20 included) while this costs 2$ per Gb. That is an order of magnitude so what am I paying for?