1. 1

This might be completely dumb, but would like to get some feedback on it.

How about a cryptocurrency that is given away freely to all your microservices, and then each transaction “costs” a certain amount relative to the processing time it took. The proof-of-work algo can be minimal (ROT13? :D) since there’s implicit trust. And the miners would just gather transactions and bunch them up in blocks, making the blockchain a source of truth for your whole system. Transactions could also maybe have the HTTP logs for the request and the response.

So, advantages would be: blockchain as source of truth, checking microservices' wallets would allow you to pinpoint the more hardware intensive services.

Makes sense? Please comment. Thanks!


  2. 9

    If there’s implicit trust, you don’t need the cryptographic overhead of a blockchain. In fact, your blockchain is just distributed, append-only request log which you can accomplish with Kafka. Wallets are just serving as a resource allocation mechanism which you can accomplish with Mesos or Kubernetes.

    This idea may make sense if you have a shared cluster that you want to open up to the world.

    1. 1

      I think public APIs requiring a proof-of-work would be rather cool. There are a few ways to do this so far but they don’t work in all situations. For example, to avoid amplification attacks, and API can require that the send send as many byte as there response will be.

    2. 0

      Relevant: https://21.co/

      1. 1

        To be clear, I think @sridatta’s comment above nails the issue here.