How We Build Code at Netflix

#1

Post by hepha1979 » Wed, Mar 09, 2016, 3:02 PM UTC

How We Build Code at Netflix
techblog.netflix.com

Re: How We Build Code at Netflix

#2

Post by mattiemass » Wed, Mar 09, 2016, 3:21 PM UTC

Very cool article. Amazing how much tooling Netflix has built themselves.

Re: How We Build Code at Netflix

#3

Post by hitekker » Wed, Mar 09, 2016, 3:30 PM UTC

mattiemass wrote: post #2

Very cool article. Amazing how much tooling Netflix has built themselves.

I believe at least some parts of the tooling were developed by an embedded team from Pivotal Labs.

Re: How We Build Code at Netflix

#4

Post by moondev » Wed, Mar 09, 2016, 3:30 PM UTC

Spinnaker is an amazing tool. Really makes it easy to confidently deploy applications via immutable infrastructure.

Re: How We Build Code at Netflix

#5

Post by sanjeetsuhag » Wed, Mar 09, 2016, 3:49 PM UTC

moondev wrote: post #4

Spinnaker is an amazing tool. Really makes it easy to confidently deploy applications via immutable infrastructure.

Can some one explain to me what immutable means in terms of "infrastructure" ?

Re: How We Build Code at Netflix

#6

Post by softawre » Wed, Mar 09, 2016, 3:52 PM UTC

sanjeetsuhag wrote: post #5

moondev wrote: post #4

Spinnaker is an amazing tool. Really makes it easy to confidently deploy applications via immutable infrastructure.

Can some one explain to me what immutable means in terms of "infrastructure" ?

You build the VM one time, deploy it to dev. If all tests pass, you deploy the exact same VM to test/stage/prod/whatever.

It's the diff between a new build (of the "same code") for each environment versus building up the VM one and deploy that.

Re: How We Build Code at Netflix

#7

Post by detaro » Wed, Mar 09, 2016, 3:53 PM UTC

sanjeetsuhag wrote: post #5

moondev wrote: post #4

Spinnaker is an amazing tool. Really makes it easy to confidently deploy applications via immutable infrastructure.

Can some one explain to me what immutable means in terms of "infrastructure" ?

Roughly that services are not upgraded in place, but completely replaced, here by creating a new image and launching it in fresh instances, then shutting down the instances running old code. Makes sure that all instances are exactly the same, vs otherwise there might be differences between freshly created and upgraded ones etc.

Re: How We Build Code at Netflix

#8

Post by hellofunk » Wed, Mar 09, 2016, 3:53 PM UTC

sanjeetsuhag wrote: post #5

moondev wrote: post #4

Spinnaker is an amazing tool. Really makes it easy to confidently deploy applications via immutable infrastructure.

Can some one explain to me what immutable means in terms of "infrastructure" ?

The article actually discusses this directly.

Re: How We Build Code at Netflix

#9

Post by pitt1980 » Wed, Mar 09, 2016, 3:55 PM UTC

bm

Re: How We Build Code at Netflix

#10

Post by moondev » Wed, Mar 09, 2016, 3:56 PM UTC

sanjeetsuhag wrote: post #5

moondev wrote: post #4

Spinnaker is an amazing tool. Really makes it easy to confidently deploy applications via immutable infrastructure.

Can some one explain to me what immutable means in terms of "infrastructure" ?

A short summary would be that your infrastructure (instances) are replaced for every deployment instead of updated in place. This is all done via continuous delivery tools (spinnaker, jenkins etc) and is very important to be able to easily scale microservices horizontally.