deforciant

Swarm is used but I have heard many companies migrating from swarm to k8s and openshift. Swarm is just unstable, network connectivity is flaky, not sure how can you run it in prod (maybe you can't?).

As for k8s - would recommend it for anything from hobby projects to large prod deployment. Easy to set up anywhere.

This article is indeed very shallow and clearly author hasn't bothered to do some research.

3 f1.micro nodes k8s on GKE for hobby side projects:)

so 84% don't want generics, right? :) I switched to Go from Python several years ago, I admit that I missed generics for the first several weeks but then just moved forward. Nowadays I don't really think I actually need them anymore.

Very interesting, what's the minimum amount of nodes required to operate it?

looks great, I really like BuntDB, already using it in project :) Glad to see this new SummitDB, will definitely try it out!

Researchers should end this madness and free the ants. I don't think that those ants are happy :/ :(

thanks, currently working on one hobby project and skipped job queue part because I thought I will need some more consideration :) Now it looks like this could fill that gap. Regarding persistence - how about adding https://github.com/docker/libkv ? For single node - BoltDB backend is more than enough and once you want to go distributed - just switch to Consul/Etcd.

javascript and "win" must not be in the same sentence

looks interesting, where can I download Dragon? :D

Hi. Hoverfly author here. I agree, messaging is vital in micro-services environment. We chose HTTP(s) as the first protocol to "virtualize" to help us better understand what additional functionality is needed (like hoverfly middleware).

The problem with 0MQ/RabbitMQ is that it's not that straightforward/transparent as in HTTP proxy. Initial thoughts to capture messages would be to use something like this http://api.zeromq.org/3-2:zmq-proxy as a forwarder.

yes, it is :)

In case of Hoverfly, it never needs read/write operations, it only writes during "capture" mode and then only reads during "virtualize" mode and that's when performance really counts, so it looks like a perfect solution.