{"id":1269,"date":"2012-11-26T17:05:21","date_gmt":"2012-11-26T23:05:21","guid":{"rendered":"http:\/\/redmonk.com\/dberkholz\/?p=1269"},"modified":"2013-04-19T21:26:52","modified_gmt":"2013-04-20T02:26:52","slug":"the-opportunity-in-packaging-netflixs-open-source-software","status":"publish","type":"post","link":"https:\/\/redmonk.com\/dberkholz\/2012\/11\/26\/the-opportunity-in-packaging-netflixs-open-source-software\/","title":{"rendered":"The opportunity in packaging Netflix&#8217;s open-source software"},"content":{"rendered":"<figure id=\"attachment_1274\" aria-describedby=\"caption-attachment-1274\" style=\"width: 480px\" class=\"wp-caption aligncenter\"><a href=\"http:\/\/dberkholz-media.redmonk.com\/dberkholz\/files\/2012\/11\/netflix_github_com.png\"><img loading=\"lazy\" decoding=\"async\" data-attachment-id=\"1274\" data-permalink=\"https:\/\/redmonk.com\/dberkholz\/2012\/11\/26\/the-opportunity-in-packaging-netflixs-open-source-software\/netflix_github_com\/\" data-orig-file=\"https:\/\/redmonk.com\/dberkholz\/files\/2012\/11\/netflix_github_com.png\" data-orig-size=\"600,420\" data-comments-opened=\"1\" data-image-meta=\"{&quot;aperture&quot;:&quot;0&quot;,&quot;credit&quot;:&quot;&quot;,&quot;camera&quot;:&quot;&quot;,&quot;caption&quot;:&quot;&quot;,&quot;created_timestamp&quot;:&quot;0&quot;,&quot;copyright&quot;:&quot;&quot;,&quot;focal_length&quot;:&quot;0&quot;,&quot;iso&quot;:&quot;0&quot;,&quot;shutter_speed&quot;:&quot;0&quot;,&quot;title&quot;:&quot;&quot;}\" data-image-title=\"netflix_github_com\" data-image-description=\"\" data-medium-file=\"https:\/\/redmonk.com\/dberkholz\/files\/2012\/11\/netflix_github_com-300x210.png\" data-large-file=\"https:\/\/redmonk.com\/dberkholz\/files\/2012\/11\/netflix_github_com.png\" class=\"wp-image-1274 \" title=\"netflix_github_com\" alt=\"\" src=\"http:\/\/dberkholz-media.redmonk.com\/dberkholz\/files\/2012\/11\/netflix_github_com.png\" width=\"480\" height=\"336\" \/><\/a><figcaption id=\"caption-attachment-1274\" class=\"wp-caption-text\">Netflix has a unique take on how to present its open-source software on GitHub.<\/figcaption><\/figure>\n<p>Today, Netflix released yet another component of its infrastructure as open-source software \u2014 this time the culprit was <a href=\"http:\/\/techblog.netflix.com\/2012\/11\/hystrix.html\">Hystrix<\/a>, a library to aid in building resilient software, while just last week Netflix opened\u00a0<a href=\"http:\/\/techblog.netflix.com\/2012\/11\/announcing-bitz4j-scalable-logging.html\">Blitz4j<\/a>, a framework for scalable logging. They join a <a href=\"http:\/\/netflix.github.com\/\">growing array<\/a>\u00a0of the core components of Netflix&#8217;s well-known cloud-based architecture.<\/p>\n<h2>The opportunity<\/h2>\n<p>Building software with a true cloud-based architecture, resilient to arbitrary (sometimes large) chunks of the infrastructure instantly disappearing from under the feet of the running application, is notoriously difficult. Netflix has spent years building and hosting on Amazon&#8217;s AWS cloud. The rest of the world benefits greatly from the knowledge and code shared by Netflix about how to keep a large-scale service up and running when it resembles the Biblical house built on sand.<\/p>\n<p>As usual, <a href=\"http:\/\/redmonk.com\/dberkholz\/2012\/07\/23\/what-is-packaging-its-all-about-the-barrier-to-entry\/\">packaging<\/a> is a great opportunity \u2014 in this case, to be the vendor who provides the lowest barrier to entry to building complex cloud software. While Netflix has released its software in a collection on GitHub, what will make it truly approachable to developers and companies who are generally unfamiliar with the cloud is aggregating and integrating all those bits together into an easy-to-install, easy-to-use bundle. When I brought this up on Twitter earlier today, Jeff Sussna <a href=\"https:\/\/twitter.com\/jeffsussna\/status\/273161313541308416\">argued<\/a>\u00a0against it:<\/p>\n<blockquote><p>Their focus is on large complex apps so not sure it&#8217;s for the &#8220;idiot-proof&#8221; market.<\/p><\/blockquote>\n<p>I would suggest that the reason\u00a0this kind of thing <strong>hasn&#8217;t<\/strong> been for the beginning user, or the smaller application is <strong>not because it shouldn&#8217;t<\/strong> but instead because <strong>it&#8217;s too difficult<\/strong> and not worth the tradeoff. If it were relatively easy to have a redundant architecture where you could essentially drop in your app, people would do it far more often. Think\u00a0<strong>convention over configuration<\/strong>\u00a0[<a href=\"http:\/\/redmonk.com\/jgovernor\/2012\/09\/28\/two-more-takes-on-opinionated-infrastructure-on-convention-over-configuration-rails-ios-and-systems-design\/\">writeup\/video<\/a>].<\/p>\n<div class=\"acc_license\"><a href=\"http:\/\/creativecommons.org\/licenses\/by-sa\/3.0\/\"><img decoding=\"async\" src=\"http:\/\/i.creativecommons.org\/l\/by-sa\/3.0\/88x31.png\" alt=\"by-sa\" \/><\/a><\/div><!--<rdf:RDF xmlns=\"http:\/\/creativecommons.org\/ns#\" xmlns:dc=\"http:\/\/purl.org\/dc\/elements\/1.1\/\" xmlns:rdf=\"http:\/\/www.w3.org\/1999\/02\/22-rdf-syntax-ns#\"><Work rdf:about=\"\"><license rdf:resource=\"http:\/\/creativecommons.org\/licenses\/by-sa\/3.0\/\" \/><\/Work><License rdf:about=\"http:\/\/creativecommons.org\/licenses\/by-sa\/3.0\/\"><requires rdf:resource=\"http:\/\/creativecommons.org\/ns#Attribution\" \/><permits rdf:resource=\"http:\/\/creativecommons.org\/ns#Reproduction\" \/><permits rdf:resource=\"http:\/\/creativecommons.org\/ns#Distribution\" \/><permits rdf:resource=\"http:\/\/creativecommons.org\/ns#DerivativeWorks\" \/><requires rdf:resource=\"http:\/\/creativecommons.org\/ns#ShareAlike\" \/><requires rdf:resource=\"http:\/\/creativecommons.org\/ns#Notice\" \/><\/License><\/rdf:RDF>-->","protected":false},"excerpt":{"rendered":"<p>Today, Netflix released yet another component of its infrastructure as open-source software \u2014 this time the culprit was Hystrix, a library to aid in building resilient software, while just last week Netflix opened\u00a0Blitz4j, a framework for scalable logging. They join a growing array\u00a0of the core components of Netflix&#8217;s well-known cloud-based architecture. The opportunity Building software<\/p>\n","protected":false},"author":6,"featured_media":1274,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","footnotes":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false},"categories":[6,8,13,24],"tags":[],"class_list":["post-1269","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cloud","category-devops","category-open-source","category-packaging"],"jetpack_featured_media_url":"https:\/\/redmonk.com\/dberkholz\/files\/2012\/11\/netflix_github_com.png","jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p23Tsn-kt","_links":{"self":[{"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/posts\/1269","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/comments?post=1269"}],"version-history":[{"count":0,"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/posts\/1269\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/media\/1274"}],"wp:attachment":[{"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/media?parent=1269"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/categories?post=1269"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/redmonk.com\/dberkholz\/wp-json\/wp\/v2\/tags?post=1269"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}