raft VS ic

etcd Raft — a library for maintaining replicated state machines (written in Go);

Have you seen this implementation? https://github.com/etcd-io/raft. I’ve used this as a starting point for our consensus with various services.

This is usual in parallel and distributed systems. For k8s, I recommend you either use Apache Zookeeper to coordinate “logical locks” for operations across pods or use the RAFT consensus protocol for scenarios where you need coordination amongst pods. For context, k8s itself uses the RAFT consensus protocol for etcd; see https://github.com/etcd-io/raft

Internet Computer blockchain (ICP) — a general-purpose blockchain system developed by the DFINITY Foundation (written in Rust);

Yes, non-rust dependencies can be a pain. We addressed this issue in three ways: 1. Sometimes, it just works™ if the crate has a copy of the C code and uses the cc crate to compile it. It's usually slow to compile C in a build script, but it works. 2. Sometimes, we write a custom BUILD script for direct dependencies and link external libraries by hand. Example: lmdb and lmdb-sys. 3. If all of the above is not an option or is too much work, we add a native library to the Docker container that runs our builds.

One thing that sticks out to me is that, while their code is open source, it has a restrictive license, the Apache License: https://github.com/dfinity/ic/blob/master/LICENSE - most open source projects opt for the MIT License.

Sources please? https://github.com/dfinity/ic/pulse talks of only ~100 commits (IC only, not including the other repos)

https://github.com/dfinity/ic/graphs/contributors You can see there are many contributors, whose own GitHub profiles show contributions to OTHER projects. For example, just clicking on one contributor, John Wiegley (Principal Engineer at DFINITY), you will see a long history of open source contributions: https://github.com/jwiegley

You can see the code here: https://github.com/dfinity/ic