[rabbitmq-discuss] Latest revision of NYTimes site is supported by RabbitMQ - launched 8 January 2014

[Ceri Storey]

(08/01/14 19:50), Paul Bell wrote:
> Michael,
>
> 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.
>
> Cordially,
>
> Paul
>
>
> On Wed, Jan 8, 2014 at 2:47 PM, Alvaro Videla <videlalvaro at gmail.com
> <mailto:videlalvaro at gmail.com>> wrote:
>
>     Michael,
>
>     Wow. This is great news ----no pun intended ;-)
>
>     It's really cool to hear this.
>
>     Regards,
>
>     Alvaro
>
>     On Wed, Jan 8, 2014 at 8:26 PM, Laing, Michael
>     <michael.laing at nytimes.com <mailto:michael.laing at nytimes.com>> wrote:
>     > Just a quick note and thank you to the RabbitMQ team for a great
>     product.
>     >
>     > Our premier online offering www.nytimes.com
>     <http://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 into
>     > "wholesale" and "retail" layers. Connection to clients is via
>     > websockets/sockjs.
>     >
>     > Upon launch today, the system autoscaled to ~500,000 users.
>     Connection times
>     > 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 one
>     > component, used everywhere, that never faltered or failed.
>     >
>     > We look forward to contributing our own code to the open source
>     community
>     > but it will be difficult to match the quality of this
>     outstanding product
>     > and its supporting team.
>     >
>     > Michael Laing
>     > Systems Architect
>     > NYTimes
>     >
>     > _______________________________________________
>     > rabbitmq-discuss mailing list
>     > rabbitmq-discuss at lists.rabbitmq.com
>     <mailto: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
>     <mailto: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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20140109/1c34d5c0/attachment.html>