458
Yet another reason to hate on the worse DB in existence (lemmy.ml)
submitted 9 months ago by to c/programmer_humor@programming.dev
45 comments fedilink hide all child comments
 
you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 9 months ago (3 children)

Based on what? It’s top notch for immutability, zero trust, proof of existence, accountability, transparency, uptime, decentralization, network resilience…

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 9 points 8 months ago* (last edited 8 months ago) (2 children)

    What about throughput, latency, schema modeling, query load balancing/routing, confidentiality, regulatory compliance, operational tooling? How easily can I write a CRUD or line of business service using it?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] -1 points 8 months ago* (last edited 8 months ago)

    Confidentiality, regulatory compliance, schema modeling (IDLs?), query load balancing (rpc infra) and operational tooling pretty good in my world now (Solana). Throughout and latency decent now (400ms conf, couple second finality, 4k tps) but obviously the type of system that needs a trustless immutable database has tradeoffs.

    How easily can you write a crud system? No clue that’s on you. A line of business service? Why the hell would that need a trustless immutable ledger. You’re barking up the wrong tree. Low level financial systems are pretty much the only thing that benefits. Small niche for proof of existence perhaps. And maybe other immutable use case things.

  • permalink
  • fedilink
  • source
  • parent