4 ms·
Those are really good points. Particularly the one about how there are so few open source systems built to scale. I think this is starting to change (slowly).
by jondubois 10y ago
Those are really good points. Particularly the one about how there are so few open source systems built to scale.
I think this is starting to change (slowly). I run such a project called SocketCluster and we recently released some Docker images and Kubernetes config files to make running SC on a distributed Kubernetes cluster super easy.
See https://github.com/socketcluster/socketcluster#introducing-scc-on-kubernetes https://github.com/socketcluster/socketcluster#introducing-s...
I think there will come a point when most open source stacks will be designed to run on one or more orchestration systems like Kubernetes, Swarm and/or Mesos.
The main problem at the moment is lack of skills in that area - There is currently a big divide between DevOps engineers and software engineers.
As a long-time open source developer, I felt somewhat out of my comfort zone learning Kubernetes but it was well worth it.
- simplify 10y agoBased on your DevOps experience, what's your opinion of Nix[1] and/or its OS? I keep hearing it solves a lot of pain for deploying systems, but I don't have any DevOps experience to evaluate it. [1] https://nixos.org/nix/ https://nixos.org/nix/
- jondubois 10y agoI haven't used Nix. Kubernetes runs pretty well on all the Linux distros that I've come across - I guess this is because K8s itself runs most of its components inside Docker containers so K8s isn't generally prone to configuration issues. That said, you still have to deal with certain host-level configs like file limits and such - So I guess for more advanced use cases something like NixOS could come in handy - I just haven't needed it yet - I'm running most of my stuff on Amazon EC2 - So I just make sure that my base AMI has the correct host configs for the kinds of use cases I deal with.