Back in 2020, while federating more than 100 service meshes across on-prem and AWS for a big hybrid cloud project, I had an idea: what if we could "split" the CAP theorem in a way that flips its limitations, enabling massive scaling far beyond traditional consensus protocols? Fast-forward five years:I started prototyping with libp2p, but the networking layer was always just a means to an end; the real goal is that CAP inversion/split for extreme distributed scaling. I think the timing is perfect given current geopolitical pushes.
Super curious to hear thoughts from folks. Any pitfalls I'm missing? Open to feedback or collaborators.
My experience with Docker is kind of ambivalent. We are using docker with docker compose on a legacy vmware stack in a corporate environment. No swarm and no docker overlay network as it does undermine firewalls. It is perfect to apply gitlow and semver to each build of each docker image, so each outcoming application stack is fully determenistic and auditable. Docker storage and network are really simple and docker is the perfect fit.
On the other side devs were asking for jenkins for that process. We run also Jenkins on Docker but it's cumbersome as it doesn't allow declarative configuration. There are dozen of plugins out there but it doesn't change the fact that the outcome is ressource hungry and slow. For now we are actually optimizing using Job-DSL plugin. We reached our target, but it was extremly time consuming and pain. For a new project I'm in, maybe we go to replace jenkins with concourseci or drone.
Imho a PaaS doesn't solve processual versioning and testing requirements. For that you still need further tools - with or without docker.
Back in 2020, while federating more than 100 service meshes across on-prem and AWS for a big hybrid cloud project, I had an idea: what if we could "split" the CAP theorem in a way that flips its limitations, enabling massive scaling far beyond traditional consensus protocols? Fast-forward five years:I started prototyping with libp2p, but the networking layer was always just a means to an end; the real goal is that CAP inversion/split for extreme distributed scaling. I think the timing is perfect given current geopolitical pushes.
Super curious to hear thoughts from folks. Any pitfalls I'm missing? Open to feedback or collaborators.