Comments on: Netflix to developers: More monkeys to come

By: William Louth

William Louth — Thu, 07 Feb 2013 20:19:25 +0000

You don’t need a monkey to introduce latency though it has been shown that if you get monkeys to write Java code they will introduce latency automatically ;-)

There are many ways to introduce latency without having to bind explicitly to an API.

http://www.jinspired.com/site/monkeying-around-with-latency-injection-at-service-points-using-qos-ace

And the same goes for dealing with resilience.

http://www.jinspired.com/site/jxinsight-opencore-6-4-ea-11-released-adaptive-safety-control

By: Barb Darrow

Barb Darrow — Thu, 07 Feb 2013 16:47:31 +0000

tagged!

By: Mark

Mark — Thu, 07 Feb 2013 16:07:43 +0000

A lot of people get monkeys mixed up. :)

By: Greg DeKoenigsberg

Greg DeKoenigsberg — Thu, 07 Feb 2013 08:05:28 +0000

Hey Barb — you need a Eucalyptus tag. ;)

By: Barb Darrow

Barb Darrow — Thu, 07 Feb 2013 07:44:15 +0000

Thank you Ariel– you’re right, i got my monkeys mixed up. Corrected. Thanks for your note.

By: Ariel Tseitlin

Ariel Tseitlin — Thu, 07 Feb 2013 07:35:45 +0000

Barb,

A small correction on your description of Latency Monkey. Latency Monkey injects a randomized latency and errors into service invocations. What you described is our Howler Monkey, which looks at various cloud limits and alerts us when we get close to those limits. The likely order of release will be Conformity Monkey next followed by Latency Monkey.

Ariel Tseitlin