News for hackers. Stuff that matters.
Re:Go After 2 Years in Production by netcraft on Tuesday August 27, 2013 @01:39PM (#6284920)
on an unrelated (to golang) note, does anyone have any experience they would like to share about iron.io? especially it vs rabbitmq or amazon sqs?
Re:Go After 2 Years in Production by carimura on Tuesday August 27, 2013 @02:03PM (#6285076)
[Disclaimer/Warning I work there and this is about Iron.]

Vs RabbitMQ: - Native cloud service over HTTP transport - Clean easy API - Scales to unlimited queues/clients - Push queues can have URL endpoints as subscribers - Highly available (our #1 priority is to keep it running at all times) - Nice UI to manage queues, stats, rate, etc. - IronWorker integration (workers as a service)

Vs SQS: - Fast, clean API - FIFO - One time delivery - Multi-cloud - Push queues / pubsub / fanout as first class feature - IronWorker integration (workers as a service)

Best way is to just try it out. It's already one of the leading cloud MQ's out there and we have a lot of big plans for IronMQ to make it the safest "bet your business" cloud message queue available.

Re:Go After 2 Years in Production by rabbitmq on Friday August 30, 2013 @04:41AM (#6300789)
RabbitMQ supports HTTP and has a clean easy API. Scales in lots of ways. Supports very high throughput on a single cheap AMI. Has awesome GUI and UI. Etc. YMMV.
Re:Go After 2 Years in Production by anfleene on Wednesday August 28, 2013 @11:59PM (#6294170)
I've used IronMq in production for about 6 months. It's easy to use but the uptime is terrible http://status.iron.io/history so if the messages are time sensitive I wouldn't recommend it. You should also queue the messages locally to ensure they end up in IronMq at all.
Re:Go After 2 Years in Production by carimura on Thursday August 29, 2013 @02:37PM (#6297684)
Sorry for your issues anfleene. Reliability is our top top priority. FWIW our uptime has been 99.9% over the past year - and this is far from where we want it to be.

We now also offer isolated clustering for production level highly available applications that need "4 nines" availability.

Re:Go After 2 Years in Production by paddyforan on Tuesday August 27, 2013 @02:03PM (#6285073)
We're friendly. Drop by get.iron.io/chat and we'll answer any and all questions you may have. :)
Re:Go After 2 Years in Production by carimura on Tuesday August 27, 2013 @02:04PM (#6285082)
that too.