News for hackers. Stuff that matters.
Re:Blockchain, the Solution for Almost Nothing by Lazare on Saturday August 22, 2020 @02:21AM (#24242101)
> private blockchain

So a database?

> AFAIK it is live and actively used.

Most things people seem to think are running on blockchain tech turn out not to be, so I'd be interested in any evidence here. Nonetheless.

> operating a database for that scale would be very complicated

They're already operating a database, so at most this is an argument that a traditional database tech wouldn't work, except...

...this is only a few billion rows, at most, right? With minimal data? It would totally, totally work. We're at a scale where a copy of "MySQL for dummies" is going to explain everything you need to know here. A moderately large number of people in this thread probably work for companies that have traditional databases that work at a larger scale or with higher demands than this.

Re:Blockchain, the Solution for Almost Nothing by davidgerard on Saturday August 22, 2020 @05:31AM (#24242929)
> Most things people seem to think are running on blockchain tech turn out not to be, so I'd be interested in any evidence here. Nonetheless.

There's a few such systems in production - in practice, they tend to use a private Ethereum or Hyperledger as a back-end data store, and 100% of the use case for using a blockchain for your private back-end data store is being able to say "blockchain!" in the press release.

Re:Blockchain, the Solution for Almost Nothing by an_opabinia on Saturday August 22, 2020 @03:17AM (#24242360)
I am not super familiar with the particular example.

But if you consider it more like an easy to cluster database with free, tamper-proof backups, it makes a lot more sense.

Re:Blockchain, the Solution for Almost Nothing by redis_mlc on Saturday August 22, 2020 @04:43AM (#24242727)
I've worked with MySQL and Postgres databases that invariably include one or two tables with over a billion rows per table. Typically the rows record user fingerprint info of some kind, either UA or location.

There is no problem with performance until schema changes are made, requiring a careful migration strategy plan (this is why DBAs get the big bucks.)

Source: DBA.