3 ms·

I am amazed at how Docker bricked on Docker Swarm so hard. I assert to this day that the only conclusion to choosing Docker Swarm is to rewrite a worse version

• voidmain0001 7y ago
  This developer, Gerhard Lazu, states otherwise regarding Kubernetes as he describes the infrastructure that he built for changelog.com based on Docker Swarm rather than K8s: https://changelog.com/podcast/254 https://changelog.com/podcast/254
• nickstinemates 7y ago
  Especially given we used to have Meetups at the office every Thursday night, where at least 1 new Orchestration project was launched/demoed every week. The initial project the team worked on was called Beam. After about 6 months and no progress to show, the conversations referenced above happened and this is the result.. Kubernetes launched at the first DockerCon[1], early 2014. Swarm was launched[2] in beta in Dec 2014. So, roughly 1 year late to market, 6 months after initial K8 launch. 1: https://www.youtube.com/watch?v=YrxnVKZeqK8 https://www.youtube.com/watch?v=YrxnVKZeqK8 2: https://blog.docker.com/2014/12/announcing-docker-machine-swarm-and-compose-for-orchestrating-distributed-apps/ https://blog.docker.com/2014/12/announcing-docker-machine-sw...
  • cpuguy83 7y ago
    I still rather like some of the output beam (libchan), just that GRPC came along and it's all history now. But yes agreed this was all completely frustrating at the time, and completely depressing now.