[okfn-labs] Operations and engineering at Netflix

Nick Stenning nick at whiteink.com
Thu Jun 28 16:34:19 UTC 2012


On 2012-06-28 10:35, Tom Rees wrote:
> Did you forget to include a URL? :)

FAIL:
http://techblog.netflix.com/2012/06/netflix-operations-part-i-going.html

Note, by the way that this is going to part of a series of posts from
Netflix ops engineers about their operations team.

-N


> On Thu, Jun 28, 2012 at 12:00 AM, Nick Stenning <nick at whiteink.com
> <mailto:nick at whiteink.com>> wrote:
> 
>     Dear all,
> 
>     Yet another interesting tidbit from around the web which talks about
>     the changes that happened in the Netflix engineering team that
>     occurred when they moved their services "to the cloud".
> 
>     Of particular interest (to me at least) are:
> 
>     - service oriented architecture -- Nf moved from a monolithic java app
>     to hundreds of small services, each with their own deployment schedule
>     - pushing responsibility for service uptime into development teams
>     - investing additional engineering capacity into building automation
>     and test tooling
> 
>     Best,
>     N
> 
>     _______________________________________________
>     okfn-labs mailing list
>     okfn-labs at lists.okfn.org <mailto:okfn-labs at lists.okfn.org>
>     http://lists.okfn.org/mailman/listinfo/okfn-labs
> 
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.okfn.org/pipermail/okfn-labs/attachments/20120628/52f8ac72/attachment-0002.sig>


More information about the okfn-labs mailing list