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 spacefight on Tuesday August 05, 2014 @03:11AM
(#8135878)
Great, I was looking something like Muut. Looks friendlier than Disqus. Before I sign up, does anyone know, on how to plan to monetize their free service?
Edit: found it - if you want to style or extend it, you can opt to pay a fee.
Re:Backend Teardown: Muut
by terop on Tuesday August 05, 2014 @03:33AM
(#8135915)
You can embed Muut on your site and it becomes a true part of the page. You'll have complete CSS control and there is no need to pay for that. The free version is a full forum and commenting solution with unlimited data and traffic.
Re:Backend Teardown: Muut
by JLehtinen on Tuesday August 05, 2014 @09:45AM
(#8136832)
Yes, embedding is done by inserting a couple of lines of html, and styling to make Muut look like the rest of your site is easy with the included CSS designer tool. You can also write CSS by hand if you wish.
Re:Backend Teardown: Muut
by courtneycouch0 on Tuesday August 05, 2014 @10:43AM
(#8137110)
Redis for us almost operates as a set of application servers. We push a great deal of logic into Lua that we compile so that tons of back and forth operations aren't necessary. This also limits the data sent back to the API servers since only the structures needed are sent back.
We're rather coupled with Redis as a result with much of the application logic in Lua and our data structure designed around Redis structure types and commands.
Re:Backend Teardown: Muut
by mxpxrocks10 on Tuesday August 05, 2014 @09:22AM
(#8136727)
we used Tokumx for http://blog.maxcdn.com/learned-stop-worrying-love-logs/ and the write performance vs mongo was incredible. I think the cluster is doing ~250,000 writes per second across six boxes with SSD space being the bottleneck. I'm really curious to spin up AerospikeDB. There's no Tokumx comparison I could find and they talk about very high reads. Curious to see write heeavy applications.
I'm testing it out and it seems pretty legit if you need a big, big key value store and don't want to wrangle redis or memcached shards.
Non-Java drivers are a bit behind, but nothing seems to have the same 95%tile latency, fast failover, SSD performance for actual read loads, and relatively easy scale out.
(me, I'm a fan of vulcanproxy[1], even if it is a bit young)
[1] - http://vulcanproxy.com/
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.
Disclaimer: CoreOS employee
Edit: found it - if you want to style or extend it, you can opt to pay a fee.
We're rather coupled with Redis as a result with much of the application logic in Lua and our data structure designed around Redis structure types and commands.
https://news.ycombinator.com/item?id=8093476
Non-Java drivers are a bit behind, but nothing seems to have the same 95%tile latency, fast failover, SSD performance for actual read loads, and relatively easy scale out.