node-replication VS ipfs-deploy

As pointed out at https://nrkernel.systems/book/, we developed some black-box techniques(https://github.com/vmware/node-replication) to convert data structures into their concurrent and NUMA-aware versions. These techniques are mostly based on state-machine replication using operation logs and replicate the state on each NUMA node.

> IPFS, Hypercore or some other protocol available to the mainstream, whether that be in Firefox or by some other means

TIL about hypercore! Looks like an interesting concept based on append-only logs. It reminds me of this work being done at VMware: https://github.com/vmware/node-replication

I've got a basic personal site with blog posts and random stuff that I also make available through IPFS. The site is made with Gatsby, a static site generator that generates a folder full of html files and resources. I host those on a normal webserver, but I also publish the files onto IPFS (using ipfs-deploy and https://pinata.cloud/ as the pinning service) and then have a DNSLink DNS record on the domain (that gets updated by ipfs-deploy) so that people with IPFS-compatible browsers can access the site through IPFS. It's also nice that it means a mirror of my site is also accessible through https://MY-DOMAIN-COM.ipns.dweb.link. I like knowing that if anything happens to my regular webserver, then as long as the domain is still up then there good ways to access my site and for anyone to help preserve my site.

I recommend Pinata [0] for IPFS pinning if you do not want to host your own IPFS node. I'm not sure when they'll start charging but it's been free since they launched and I believe Infura [1] also has free pinning. Cloudflare [2] is a good alternative gateway to use. For deployment I use this deploy tool [3] which makes it as simple as `ipd -p pinata my-app`

[0] https://pinata.cloud/

[1] https://infura.io

[2] https://blog.cloudflare.com/distributed-web-gateway/

[3] https://github.com/ipfs-shipyard/ipfs-deploy