• locuester@lemmy.zip
    link
    fedilink
    English
    arrow-up
    6
    arrow-down
    2
    ·
    20 hours ago

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

    • chaospatterns@lemmy.world
      link
      fedilink
      English
      arrow-up
      5
      ·
      edit-2
      3 hours ago

      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?

      • locuester@lemmy.zip
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        1 hour 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.