varyinteresting
varyinteresting on Hacker News
Re:Mongrel2 Is "Self-Hosting"
on Thursday June 17, 2010 @03:09PM (#1440036)
Not quite. I wasn't talking about how the backend communicates. I'm a big fan of zeromq too but there are many types of messaging and it is a must once you start adding more than a few servers. As I see others have mentioned, you're going to have problems with parsing speed at some point. What happens when you need to scale out to handle all the requests on the front end?
How is HA going to be handled? WIll it be easy enough to have an Active/Active of the mongrel server? How do you get away from a single point of failure?
Re:Mongrel2 Is "Self-Hosting"
on Thursday June 17, 2010 @02:56PM (#1439995)
That is great. I'd never heard of libebb before but have a couple of things I can already use this for. Thanks for sharing.
Re:Mongrel2 Is "Self-Hosting"
on Thursday June 17, 2010 @02:01PM (#1439781)
How is this different than using Layer 4 routing/load-balancing? If you are already scaling to multiple backends then you're probably likely to have access to more than 1 or 2 public facing IPs if you have to ensure everything inbound is on port 80. Just use sub-domains with different DNS A records. You listen on port 80 and then route to your backend application farm. The load balancers already have various means to monitor health on the backend and you can scale to 100Gbs speed already if you have the budget.
Check out LVS if you want open-source. HAProxy can handle this in a limited fashion. Then if you have gone big already then you can probably afford a Brocade ServerIron, Citrix Netscaler or F5 Big-IP.
Or am I missing something here?