[rabbitmq-discuss] Latest revision of NYTimes site is supported by RabbitMQ - launched 8 January 2014
michael.laing at nytimes.com
Tue Jan 14 17:14:29 GMT 2014
We're busily improving our monitoring and resilience at the moment - there
is nothing like a real load to shake things out!
I will notify this list when we have a post somewhere or a presentation.
I'll be talking at the FOSDEM conference in Brussels 1-2 Feb in the NoSQL
track - and there will be other conferences this year as well.
Meanwhile, if there are particular pieces people are most interested, let
me know via the list and I will prioritize them in our posts and
On Thu, Jan 9, 2014 at 8:00 AM, Ceri Storey <ceri at lshift.net> wrote:
> (08/01/14 19:50), Paul Bell wrote:
> That's very exciting news.
> Have you published any documents on this architecture, i.e., stuff you
> can share publicly?
> I'll second this. I'm very curious as to what kind of toplogy they're
> using, and how they've designed to make it resilient across zones .
> I'd be most interested in seeing them.
> On Wed, Jan 8, 2014 at 2:47 PM, Alvaro Videla <videlalvaro at gmail.com>wrote:
>> Wow. This is great news ––no pun intended ;-)
>> It's really cool to hear this.
>> On Wed, Jan 8, 2014 at 8:26 PM, Laing, Michael
>> <michael.laing at nytimes.com> wrote:
>> > Just a quick note and thank you to the RabbitMQ team for a great
>> > Our premier online offering www.nytimes.com has a new look and new
>> > underpinnings, now including a messaging architecture implemented using
>> > RabbitMQ.
>> > This architecture - nyt⨍aбrik - has dozens of RabbitMQ instances spread
>> > across 6 AWS zones in Oregon and Dublin. The instances are organized
>> > "wholesale" and "retail" layers. Connection to clients is via
>> > websockets/sockjs.
>> > Upon launch today, the system autoscaled to ~500,000 users. Connection
>> > remained flat at ~200ms.
>> > nyt⨍aбrik provides subscription services for breaking news, video feeds,
>> > etc. and will add more event based services. It also supports individual
>> > messaging related to subscription status for registered users.
>> > This system would not have been possible without RabbitMQ. It was the
>> > component, used everywhere, that never faltered or failed.
>> > We look forward to contributing our own code to the open source
>> > but it will be difficult to match the quality of this outstanding
>> > and its supporting team.
>> > Michael Laing
>> > Systems Architect
>> > NYTimes
>> > _______________________________________________
>> > 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
> rabbitmq-discuss mailing listrabbitmq-discuss at lists.rabbitmq.comhttps://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss