I'm only going to reply this last time as I come to HN to get away from reddit style back and forth arguments. They don't say that standard databases can't han

I'm only going to reply this last time as I come to HN to get away from reddit style back and forth arguments. They don't say that standard databases can't handle this. They say that they can do it cheaper and faster without them, because you don't need a bunch of the features. They are literally telling you that their solution is simpler not revolutionary. You are conflating two very different things, the production and indexing - and then consumers. > - Blockchain isn't the only thing to have an immutable log. Apache Kafka is one, and is being used at scale that dwarfs anything in crypto space Sure, and doesn't solve the problem here as you have already told me. Kafka would be ridiculous overkill IMO for the part it would play. The problem is simpler than kafka is designed for, so it makes sense that someone could make a simpler tool to handle it. > Even though, again, traditional systems can probably handle all this on a free tier of any cloud hosting provider That very much depends on your users - it's this kind of statement that makes me think you're not picturing what this actually is. > slap a traditional (I'd say conservative) JSON-RPC API on top, Yes, this exact API is very much a requirement for this kind of service. As a final thought, if you think you can throw this together for a large customer base easily and host it basically for free while having better performance - go for it. You'll make money because the alternative options are expensive.