ezmobius

There already exists an nginx module that talks to redis, it just does basic gets and doesn't support the entire redis protocol but it's a Start. Sorry don't have a link handy and I'm on my iPhone, a kittle google juice will find it for you.

Engine Yard is hiring for multiple positions. We're hiring sysadmins, app support engineers as well as ruby engineers to work on our cloud platform.

If you like working with nosql, aws, cloud, linux, nginx, ruby, unicorn, passenger, haproxy, deployment automation tools, chef. TDD, BDD, pair programming etc, then you will like working here.

Send an email to jarnold@engineyard.com (Joe Arnold) with an intro and a resume.

Tender or zendesk are both great products, and they each have different use cases. We use both of them for our support ticketing for engineyard. We use tender for our community support/forum/faq type of stuff d we use zendesk for our paid 24/7 support needs.

Both of these platforms have great API's and good email integration and they are both highly recommended.

It can but you will not have access to the secondary drbd'd system on the rds service, it is strictly for ha and not for read scaling.

Amazon's 'replication' is not mysql replication though, it is a drbd block level replication and can not be used for scaling reads like normal mysql slaves can be used.

gentoo

Collectd, I swear by it, running it on thousands of hosts without issues.

the mysql query cache is mostly useless anyway. The innodb_bufer_pool is what saves you and it does not throw out the whole cache when you update an item.

Funny thing is that we told github that gfs would not scale for them over a year ago, we also outlined how to move to a shared nothing chunk server architecture. They didn't take our advice so it's mostly their own architecture decisions that were holding them back with regards to gfs.

Anyway there seems to be plenty of airchair quarterback on this one. The real story is that we can't afford to host them for free anymore.

yeah but it doesn't look like this will work with a rabbitmq broker since it implements amqp 0.10, rabbit is currently 0.8 mqp compliant so you would have to use qpid as the amqp server afact. Still pretty cool though.

I'm one of the founder of http://engineyard.com

except that amazon has invested in engine yard and we have a cloud service that runs on top of AWS(http://www.engineyard.com/cloud-services) so it's not so humorous.

yup we host lots of stuff on aws, why is that an issue?

We already support passenger and have for some time now. It works very well for most cases but mongrel is still a better choice for some apps that can't run on passenger because of threading use or the need to use amqp etc

eeww, AGPL is a big fail here if you want folks to actually use this thing.

feel free to write the code in any language or platform you want, we don't care.

it runs on merb actually.

multi-tenant architectures are the geocities of cloud computing. This is the main problem with something like gae, if they have an internal problem it takes down their entire cloud and all the apps with it.

yup, it turns out rails is a web framework and almost all web frameworks scale the same way these days ;)

I guess I spoke too soon and they did add support for multiple ports through the sam lb access point. So http and https can be served from the same lb. This makes the lb much more interesting.

Here's my take on these features...

Monitoring and autoscaling I'll pass on. You can get better monitoring with collectd for free and autoscaling based on just load age or disk util and not app specific stuff is plain crazy.

The load balancer is pretty nice but I'll stick with haproxy until you can do httpand https on the same lb and also currently you can only do CNAME dns so no foo.com only www.foo.com and wildcard subdomains don't work unless you use tinydns(bind can't do it)

So I feel like this is a good start but I won't be using any of these services until they get more fully baked. The load balancer is the most interesting part but is currently seriously flawed.

1. So far I have tested it with 2000 agents and was not pushing the limit of the broker, rabbitmq is know to handle a lot more connections then this. my goals/estimations will be around probably 5k agents per rabbit cluster with a need to federate/shard nanite systems after they grow that big.

2. This works on LAN or across the net transparently, so it can be used across data centers easily.

yes i think it is a bug in yc with .at domains as anytime my blog shows up here it has that dot in front of it

cool thanks

I don't see anything in this article about DoS, where are you getting that from? these are benchmarks against static files, still very impressive but not DoS protection.

If you are building apps in ruby there is a high level AWS management platform I built here: http://engineyard.com/solo.

decidedly yes

that always happens to my blog domain when it gets posted here. Something with the two letter TLD and the way yc links urls

The open cloud manifesto is full of hot air anyway so this is no surprise.

no code is faster then no code.