News for hackers. Stuff that matters.
Re:Backend Teardown: Muut by pquerna on Tuesday August 05, 2014 @01:27AM (#8135675)
Curious on the Docker usage in production, are they using host networking or another way of doing load balancer integrations?

(me, I'm a fan of vulcanproxy[1], even if it is a bit young)

[1] - http://vulcanproxy.com/

Re:Backend Teardown: Muut by terop on Tuesday August 05, 2014 @04:33AM (#8136031)
I'm the frontend developer of Muut.

We are not using Docker on the main API server since last time we checked it out the CoreOS / Docker combo could not deal with the load we had. Now that both of these are much more stable we are going to have another shot.

Re:Backend Teardown: Muut by nodesocket on Tuesday August 05, 2014 @02:01AM (#8135754)
Vulcan looks neat because it is configured centrally via etcd (thanks CoreOS). Simply push changes to etcd and vulcan hosts ingest the changes. Though, it is hard to imagine a much better http reverse proxy than nginx.
Re:Backend Teardown: Muut by courtneycouch0 on Tuesday August 05, 2014 @10:38AM (#8137089)
We are using the host networking for the services currently on Docker. Load balancer and primary API endpoints are all running outside of Docker so there isn't a huge networking load for us with Docker.
Re:Backend Teardown: Muut by robszumski on Tuesday August 05, 2014 @02:37AM (#8135811)
I'm using Vulcan on CoreOS to route between a few backend containers for several static sites and it has been going great for a few months now.

Disclaimer: CoreOS employee

Re:Backend Teardown: Muut by mxpxrocks10 on Tuesday August 05, 2014 @04:50AM (#8136060)
CoreOS is looking really tight.
Re:Backend Teardown: Muut by mxpxrocks10 on Tuesday August 05, 2014 @01:28AM (#8135684)
good question. I'll let them know about this thread. I don't know off hand. Vulcanproxy looks good. First time I've seen it.