[rabbitmq-discuss] Question on who usually manages brokers

[Kamil Choudhury]

Once an IT organization grows beyond a certain size, I think it's natural for the ownership of production messaging infrastructure to be transferred over to a dedicated sysops team. 

That said, there is something to be said for not relinquishing too much control to dedicated teams. I prefer to maintain control of my development infrastructure: the overhead of coordinating with external teams on the numerous config changes involved during the development period of any project is a horrible productivity sink. 

YMMV. 
________________________________________
From: rabbitmq-discuss-bounces at lists.rabbitmq.com [rabbitmq-discuss-bounces at lists.rabbitmq.com] on behalf of Pieter de Zwart [pdezwart at rubiconproject.com]
Sent: Monday, June 20, 2011 2:50 PM
To: Alexis Richardson; James Carr
Cc: rabbitmq-discuss
Subject: Re: [rabbitmq-discuss] Question on who usually manages brokers

Hey James,

We are actually dealing with this very problem right now, and maybe our
experience can help inform your decision.
We have been using RabbitMQ for a little over a year. It started off as a
cool side project, because we thought it would be an interesting tool to
have. Unfortunately, RabbitMQ worked so well that it soon became a mission
critical portion of our system, even though the underlying install/setup was
done by non-operations people. However, because Rabbit is so solid, we have
yet to have any negative consequences (knock on wood.)

We are now a mid-size business, and I am pushing hard to get ops to take
over the basic setup and administration of Rabbit. The way it is treated and
used is much like Memcache or any other service: I have people on my team
who deeply understand how to use it and architect applications around it,
but they work in conjunction with Ops who administers and manages it.

My take aways are therefore:
Rabbit became mission critical really quickly
+ There are people better suited at dealing with servers, hardware,
configurations, etc.
+ I don't like to wake up at 3am on Sunday
= Ops is taking ownership.

me

On 6/17/11 10:16 AM, "Alexis Richardson" <alexis at rabbitmq.com> wrote:

> James
>
> I don't think there is 'one' reply to this.  Ultimately, IMO, the
> infra should belong to an ops team when the scale of the company
> merits that.
>
> alexis
>
>
> On Thu, Jun 16, 2011 at 2:59 PM, James Carr <james.r.carr at gmail.com> wrote:
>> Hey All,
>>
>> We're prepping to do a major roll out of using rabbitmq at work and
>> one of the questions that has come up is who would be responsible for
>> owning the messaging infrastructure. Although we have some ideas I'd
>> be interested in hearing how other midsized companies (500-2000
>> employees) go about this.
>>
>> Thanks,
>> James
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss



_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss at lists.rabbitmq.com
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss