<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Lenny for your Thoughts - Medium]]></title>
        <description><![CDATA[Perspectives on developer tools, distributed systems, cloud infrastructure and security with side helping of SJ Sharks rants - Medium]]></description>
        <link>https://medium.com/lenny-for-your-thoughts?source=rss----4c96f577453e---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Lenny for your Thoughts - Medium</title>
            <link>https://medium.com/lenny-for-your-thoughts?source=rss----4c96f577453e---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:20:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/lenny-for-your-thoughts" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Infrastructure 3.0: Building Blocks for the AI Revolution]]></title>
            <link>https://medium.com/lenny-for-your-thoughts/infrastructure-3-0-building-blocks-for-the-ai-revolution-f141d55b4202?source=rss----4c96f577453e---4</link>
            <guid isPermaLink="false">https://medium.com/p/f141d55b4202</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[venture-capital]]></category>
            <category><![CDATA[infrastructure]]></category>
            <dc:creator><![CDATA[Lenny Pruss]]></dc:creator>
            <pubDate>Mon, 04 Dec 2017 01:29:27 GMT</pubDate>
            <atom:updated>2017-12-04T01:33:17.971Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This post first appeared in VentureBeat on </em><a href="https://venturebeat.com/2017/11/28/infrastructure-3-0-building-blocks-for-the-ai-revolution/"><em>November 28, 2017.</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/634/1*w1NXegZhs-ntGUnSUbPdUw.jpeg" /></figure><p>By<a href="https://twitter.com/lxbrun/status/908712249379966977"> any measure</a>, we’ve entered into the Age of Machine Learning and Artificial Intelligence (‘ML/AI’). The confluence of massive data, cheap storage, elastic compute, and algorithmic advances, particularly in deep learning, has given rise to applications that previously were confined to the pages science fiction novels.</p><p>Machines now surpass humans in complex <a href="https://www.theverge.com/2016/3/9/11185030/google-deepmind-alphago-go-artificial-intelligence-impact">strategy games</a>, to say nothing of <a href="https://www.forbes.com/sites/michaelthomsen/2015/02/19/microsofts-deep-learning-project-outperforms-humans-in-image-recognition/#574de6c3740b">image recognition</a>, <a href="https://www.microsoft.com/en-us/research/blog/microsoft-researchers-achieve-new-conversational-speech-recognition-milestone/?ranMID=24542&amp;ranEAID=TnL5HPStwNw&amp;ranSiteID=TnL5HPStwNw-p8HgHmfL9CasYSd53bp_fA&amp;tduid=(a560edd1b5cf6016c02b1b0572ac1054)(256">speech transcription</a>, and other advances that begin to complicate our assumptions about what is and isn’t uniquely human.<a href="https://www.forbes.com/sites/eladnatanson/2017/06/22/artificial-intelligence-smart-assistants-the-next-big-thing-in-computing/#5790077a4252"> Voice-based personal assistants</a> are commonplace; fully-autonomous vehicles seem<a href="https://www.nytimes.com/2017/10/17/nyregion/driverless-cars-manhattan.html?_r=0"> just around the bend</a>.</p><p>Given these recent advances, much of the dialogue around ML/AI has centered disproportionately, albeit understandably, on breakthroughs in algorithms and their applications. Notably absent in the discussion has been any mention of the infrastructure underlying these intelligent systems.</p><p>Just as in the earliest days of computing where one needed to be expert in assembly language, compilers and operating systems to develop a simple application, so today you need an<a href="https://venturebeat.com/2017/10/24/lyfts-biggest-ai-challenge-is-getting-engineers-up-to-speed/"> army of stats and distributed systems PhDs to build and deploy AI at scale</a>. The abstractions and tooling necessary to make ML/AI usable are the missing link. The upshot is that ML/AI remains a limited and expensive discipline reserved for only a few elite engineering organizations.</p><p>Ultimately, this is relates to a lag in the evolution of infrastructure, which, to date, has been far outpaced by innovation in machine learning techniques. Put simply: the systems and tooling that helped usher in the current era of practical machine learning are ill-suited to power future generations of the intelligent applications they spawned.</p><p>Going forward, an entirely new toolchain is necessary to unlock the potential of ML/AI; to make it operational and usable, let alone approachable, for developers and enterprises. It stands to reason, then, that the next great opportunity in infrastructure will be to provide the building blocks for systems of intelligence.</p><p><strong><em>From Infrastructure 1.0 to 2.0 and Beyond</em></strong></p><p>Applications and infrastructure evolve in lock-step:</p><p>Advances in hardware or systems software cascade up the stack, enabling new breeds of applications. Those apps mature, come to strain their underlying resources, catalyzing a subsequent cycle of innovation at the infrastructure layer. The rise of better, faster, cheaper building blocks invariably leads to applications that deliver previously unforetold experiences to end-users. This ebb and flow forms the contours of a technical legacy that stretches from punch-cards to Pong to Powerpoint to Pinterest.</p><p>The commercial Internet that came of age in the late nineties and early aughts owes its existence to the x86 instruction set (Intel), the standardized operating system (Microsoft), the relational database (Oracle), Ethernet networking (Cisco), and networked data storage (EMC). Amazon, eBay, Yahoo and even the earliest iterations of Google and Facebook were built on this backbone we call Infrastructure 1.0.</p><p>Yet as the Web matured, growing from 16 million users in 1995 to over 3 billion by the end 2015, the scale and performance requirements of applications morphed. It was no longer feasible, much less economical, for Webscale giants to run their businesses on the backs of technologies developed during and for the client-server era.</p><p>Instead, these companies looked inward. Coupling superior technical expertise with parallel computing research from academia, the Googles, Facebooks and Amazons of the world defined a new class of infrastructure that was scale-out, programmable, (often) open source, and commodity. This category of technologies — Linux, KVM, Xen, Docker, Kubernetes, Mesos, MySQL, MongoDB, Kafka, Hadoop, Spark, and many others — defined the cloud era. My colleague Sunil Dhaliwal described this shift as <a href="http://www.amplifypartners.com/infrastructure-20/">Infrastructure 2.0</a>.</p><p>Ultimately, the technologies of this generation were purpose-built for scaling the Internet to billions of end-users and storing information captured from those users efficiently. In doing so, the innovations of Infrastructure 2.0 catalyzed a dramatic acceleration in data growth. Combined with virtually endless parallel compute and algorithmic advances, the stage was set for today’s era of practical machine learning.</p><p><strong><em>Infrastructure 3.0: The Building Blocks of Intelligent Systems</em></strong></p><p>Infrastructure 2.0 was ultimately concerned with the question of “how do we connect the world?” Today’s generation of technology rephrases the question to ask “how do we make sense of it?”</p><p>This distinction — connectivity vs. cognition — is what makes <a href="https://medium.com/@karpathy/software-2-0-a64152b37c35">ML/AI radically different from software of previous generations</a>. The computational challenge of coding cognition is that it inverts the classical programming paradigm. Whereas in traditional applications, logic is hand-coded to perform a specific task, in ML/AI, training algorithms infer logic from troves of data. That logic is then implemented to make decisions and predictions about the world.</p><p>The result is an application that is ‘smart,’ but exceptionally data-intensive and computationally-expensive. These properties make ML/AI a poor fit for the multi-purpose, generic <a href="https://en.wikipedia.org/wiki/Von_Neumann_architecture">Von Neumann</a> computing paradigm of the last seventy-plus years. Instead, ML/AI represents a foundational new architecture that necessitates a rethink of infrastructure, tooling and development practices.</p><p>To date, however, the preponderance of research and innovation in ML/AI has been dedicated to new algorithms, model training techniques and optimizations. The irony is that only a<a href="https://papers.nips.cc/paper/5656-hidden-technical-debt-in-machine-learning-systems.pdf"> tiny fraction of the code in ML/AI systems is devoted to learning or prediction</a>. Rather, the majority of complexity manifests in data preparation, feature engineering, and operationalizing the distributed systems infrastructure necessary to perform these tasks at scale.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8JTy8rezPE8vxuVOjujPpA.png" /></figure><p>Building and deploying ML/AI successfully requires a complex, carefully-coordinated workflow involving multiple discrete systems. First data needs to be ingested, cleaned and labeled. Then, the appropriate properties, known as features, upon which prediction is based must be determined. Finally, models need to trained, validated, served and continuously optimized. From start to finish, this process may take many months, even for the most technically-proficient organizations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wGi2dHvcM5XP_QfcStB6MA.png" /><figcaption>ML/AI Workflow (Amplify Partners)</figcaption></figure><p>For ML/AI to reach its full potential, it must graduate from the academic discipline it is today into an engineering one. What that practically means is there need to be new abstractions, interfaces, systems and tooling to make developing and deploying intelligent applications facile for developers.</p><p>These requisite evolutions are not tiny shifts in abstraction or incremental process improvements. Rather, they are disruptive, foundational changes in both systems design and development workflow.</p><p>Correspondingly, at every layer of the stack we’re beginning see new platforms and tools emerge that are optimized for the ML/AI paradigm. The opportunities are abundant:</p><ul><li>Specialized hardware with many computing cores and high bandwidth memory (HBM) very close to the processor die. These chips are optimized for highly parallel, numerical computation that is necessary to perform the rapid, low-precision, floating-point math intrinsic to neural networks.</li><li>Systems software with hardware-efficient implementation that compiles computation down to the transistor level.</li><li>Distributed computing frameworks, for both training and inference, that can efficiently scale out model operations across multiple nodes.</li><li>Data and metadata management systems to enable reliable, uniform, and reproducible pipelines for creating and managing both training and prediction data.</li><li>Extremely low-latency serving infrastructure that enables machines to rapidly execute intelligent actions based on real-time data and context.</li><li>Model interpretation, QA, debugging and observability tooling to monitor, introspect, tune and optimize models and applications at scale.</li><li>End-to-end platforms that encapsulate the entire ML/AI workflow and abstract away complexity from end-users. Examples include in-house systems like <a href="https://eng.uber.com/michelangelo/">Uber’s Michelangelo</a> and <a href="https://code.facebook.com/posts/1072626246134461/introducing-fblearner-flow-facebook-s-ai-backbone/">Facebook’s FBLearner</a> and commercial offerings like <a href="http://www.determined.ai/">Determined AI</a>*.</li></ul><p>Just as the last decade witnessed the emergence of the<a href="https://github.com/cncf/landscape/"> cloud-native stack</a>, so too over the next several years we expect a vast infrastructure and tooling ecosystem to coalesce around ML/AI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1yZ-t0B8W1wPuE_JSfaGLA.png" /><figcaption>Preliminary Infrastructure 3.0 Stack (Amplify Partners)</figcaption></figure><p>Collectively, the innovations of this epoch — Infrastructure 3.0 — will be about unlocking the potential of ML/AI and providing the building blocks for intelligent systems. As with previous generations, there will be new projects, platforms and companies that emerge that challenge the current incumbency. The arms dealers for this imminent ML/AI revolution promise to be infrastructure giants of tomorrow.</p><p><em>A giant thank you to </em><a href="http://etrain.github.io/"><em>Evan Sparks</em></a><em> of </em><a href="http://www.determined.ai/"><em>Determined AI</em></a><em>, </em><a href="http://www.bailis.org/"><em>Peter Bailis</em></a><em> of </em><a href="http://dawn.cs.stanford.edu/"><em>Stanford’s DAWN</em></a><em>, </em><a href="https://people.eecs.berkeley.edu/~jegonzal/"><em>Joey Gonzalez</em></a><em> and </em><a href="https://people.eecs.berkeley.edu/~rkn/"><em>Robert Nishihara</em></a><em> of </em><a href="https://rise.cs.berkeley.edu/"><em>UC Berkeley’s RISELab</em></a><em>, and my colleagues at Amplify Partners for their perspective and input.</em></p><p><em>* Amplify Partners is an investor in Determined AI.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f141d55b4202" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lenny-for-your-thoughts/infrastructure-3-0-building-blocks-for-the-ai-revolution-f141d55b4202">Infrastructure 3.0: Building Blocks for the AI Revolution</a> was originally published in <a href="https://medium.com/lenny-for-your-thoughts">Lenny for your Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Developer-Driven Economy: How the Developer has become the Organization’s Most Influential…]]></title>
            <link>https://medium.com/lenny-for-your-thoughts/the-developer-driven-economy-how-the-developer-has-become-the-organization-s-most-influential-d74ed11207b?source=rss----4c96f577453e---4</link>
            <guid isPermaLink="false">https://medium.com/p/d74ed11207b</guid>
            <dc:creator><![CDATA[Lenny Pruss]]></dc:creator>
            <pubDate>Fri, 01 Dec 2017 19:15:33 GMT</pubDate>
            <atom:updated>2015-06-02T22:20:05.456Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Developer-Driven Economy: How the Developer has become the Organization’s Most Influential Power Broker</h3><p>In 2003 Nicholas Carr published a piece in the Harvard Business Review which famously promulgated <a href="http://hbr.org/2003/05/it-doesnt-matter/ar/1">IT doesn’t matter</a>. Carr predicted that as we leave a world defined by scarcity of IT resources and enter one where “the core functions of IT — data storage, data processing, and data transport — have become available and affordable to all,” technology will cease being a source of competitive advantage for businesses altogether. Many at the time believed Carr was forecasting the death of IT in the enterprise.</p><p>Sure enough, it took maybe 5–7 years to get to Carr’s dystopian reality as cloud, open source and mobile crushed barriers to innovation, distribution and adoption of IT. However, a funny thing has happened: instead of IT ceasing to matter it has become table stakes. With ubiquitous access to infrastructure, software and software development tools in particular, we’re seeing <a href="http://online.wsj.com/articles/SB10001424053111903480904576512250915629460">software eat the world</a>.</p><p>As technology has shifted from enabler of business process, to enabler of product or service, to the very product or service itself, we’ve seen IT transform from a cost center that is adjunct to core business to a profit center that is its lifeblood.</p><p>It was during this transformation that the power dynamic within the workplace flipped from the c-suite to the basement; from the employees clad in Armani suits with tie clips to those wearing hoodies with sandals. Consequently, we’ve seen the developer become the most prized resource in the modern organization, and it is this trend that lends itself to an enormous investment opportunity.</p><p><strong><em>Devs as the Go-to-Market</em></strong></p><p>Developers are your <a href="http://www.chasminstitute.com/methodology/technologyadoptionlifecycle/tabid/89/default.aspx">innovators and early adopters</a>; they are the gatekeepers for new technologies and often decide which new tech succeeds and which fails either directly or indirectly (look no further than iOS and Windows — win the developer, win the platform war). Appropriately they have become the most powerful distribution channel for IT in the enterprise.</p><p>Devs often become catalysts for social communities which help spread new products and technologies organically, and their API-driven tools create the potential for powerful two-sided platforms. There are network effects to be taken advantage of here.</p><p>Moreover, the trend towards DevOps (and now BizDevOps) — characterized by the convergence of software development cycles and IT operations (and all business activities) — has effectively blurred the line between developer and sysadmin (and pretty much every other employee). Those tools which shrink developer time-to-value (aka time-to-code written) and offer frictionless onboarding, often multiply through the organization. From <a href="http://splunk.com/">Splunk</a> and <a href="http://logentries.com/">Logentries</a>, to <a href="http://puppetlabs.com/">Puppet</a> and <a href="http://getchef.com/">Chef</a>, to <a href="http://newrelic.com/">New Relic</a>, to <a href="http://mongodb.com/">Mongo</a>, to <a href="http://datadog.com/">Datadog</a>, we’re seeing the emergence of companies at every layer of the stack who succeed by winning the heart and mind of the developer.</p><p><strong><em>Devs as the End-Market</em></strong></p><p>There’s been a lot of talk about a renaissance in the dev tool market and it makes perfect sense: as dev teams become an organizational profit center the tools that make them more productive become that much more valuable.</p><p>The dev tool market is constantly evolving, but ultimately can be broken down into three categories which delineate the development lifecycle: writing code, testing code and running code. Within each of these segments we’re seeing companies who are fundamentally changing the way applications are built and shipped.</p><p>Tools from vendors like <a href="http://github.com/">GitHub</a>, <a href="http://slack.com/">Slack</a> and upstarts like <a href="http://bowery.io/">Bowery</a> are helping devs write, manage and collaborate around code. Trends around continuous delivery and integration have compressed release cycles and made companies more agile and responsive to customers thanks to companies like <a href="https://circleci.com/">CircleCI</a>, <a href="http://rainforestqa.com/">Rainforest</a>, and <a href="https://codeclimate.com/">CodeClimate</a>. Finally, the toolkit to ship and run code at scale is being reconstructed with the developer in mind. Infrastructure is becoming more open, more programmable and thus more developer-friendly. Products and platforms such as <a href="http://docker.com/">Docker</a> and <a href="http://digitalocean.com/">Digital Ocean</a> are rethinking operations and infrastructure altogether with the developer at the center. Companies like <a href="http://flynn.io/">Flynn</a> are even further on the bleeding edge, trying to wholly productize the role of ops teams. All of this implies that devs don’t have to mess with config files or worry about provisioning servers and databases and can just focus on their code, knowing their app will run and scale in any environment.</p><p>_ _ _ _ _ _ _ _ _ _</p><p>We’ve heard incessantly for the last several years about how the enterprise is being consumerized; how business apps are all about beautiful UX/UI, how BYOD and BYOA have broken down the corporate perimeter and how the procurer of IT is the end-user. What we haven’t heard much about is how the developer has become the biggest power broker in this new paradigm.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d74ed11207b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lenny-for-your-thoughts/the-developer-driven-economy-how-the-developer-has-become-the-organization-s-most-influential-d74ed11207b">The Developer-Driven Economy: How the Developer has become the Organization’s Most Influential…</a> was originally published in <a href="https://medium.com/lenny-for-your-thoughts">Lenny for your Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Most Important SaaS Metric Nobody Talks About: Time-to-Value (‘TtV’)]]></title>
            <link>https://medium.com/lenny-for-your-thoughts/the-most-important-saas-metric-nobody-talks-about-time-to-value-ttv-40815bd16196?source=rss----4c96f577453e---4</link>
            <guid isPermaLink="false">https://medium.com/p/40815bd16196</guid>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Lenny Pruss]]></dc:creator>
            <pubDate>Fri, 01 Dec 2017 19:15:02 GMT</pubDate>
            <atom:updated>2015-06-02T22:24:08.005Z</atom:updated>
            <content:encoded><![CDATA[<p>In a world where applications are delivered via cloud and distributed across billions of Internet-connectedend-points, we’ve seen barriers to entry, adoption and innovation compress byan order of magnitude or two, if not crushed altogether. Compound this by advances in application and data portability and the implication for technology vendors competing in this global, all-you-can-eat software buffet is that customers’ switching costs are rapidly approaching zero. In this environment it’s all about the best product, with the fastest time-to-value and near zero TCO. And it’s this second point — time-to-value (TtV) — that I want to dig in on a bit because it tends to be the one glossed over most often.</p><p>I’ll start with an anecdote …</p><p>A portfolio company of ours delivers a SaaS platform that competes with legacy, on-prem offerings from large infrastructure software vendors. In its early days the company had fallen into the enterprise sales trap: spending weeks, if not months, with individual customers doing bespoke integration and support work. About a year in when we finally decided to open up the beta to everyone, sign-ups shot up, but activity in new accounts was effectively nil. What was going on?</p><p>Simply, customers didn’t know what to do with the software once in their hands. Spending months with large accounts did inform some fundamental product choices, but at the cost of self-service. Our product was feature-bloated, on-boarding flow was clunky and the integration API was neglected and poorly documented.</p><p>In a move that, I believe, ultimately saved the company, we decided to create a dedicated on-boarding automation team within product. Sure enough, in the months that followed, usage spiked and the company was off to the races.</p><p>The takeaway is that highest priority should be given to building software that just works, and that means focusing relentlessly on reducing or eliminating altogether the time investment to fully deploy your solution in production. Ideally, you want customers to derive full value from your offering in mere minutes, if not seconds. To do so, <em>treat on-boarding as a wholesale product within your offering and devote engineering resources to it</em>. Find religion about optimizing TtV!</p><p>Below is by no means a complete list, but instead a few lessons that I’ve taken away from my experience with our portfolio that many SaaS companies should internalize in their product and go-to-market strategies to help optimize TtV:</p><p><strong><em>Simplicity wins…be feature-complete, not feature-rich: </em></strong>This is a fairly obvious but subtle point that often evades even the most talented product teams: the defining characteristic of a simple (read: good) product is not the <em>abundance</em> of features but rather the <em>relevance</em> of those features to its users. This stands in stark contrast to the old paradigm of CIO-inspired products that were over-engineered and feature-bloated. The challenge in the new paradigm is what might be relevant to one customer may be entirely worthless to another. The solution is focus, either in product or in market.</p><p>The always-better option in my mind is to narrow your product focus. Do one thing incredibly well. Tackle the single, most acute — but universal — pain point and ingrain yourself in your customers’ workflow…then expand horizontally. Value needs to be delivered from day one, but features can be revealed over time. Ultimately, it’s about understanding your unique <a href="http://www.heavybit.com/library/video/2014-11-04-jerry-chen">unit of value</a> and exploiting that with your customers. <a href="http://slack.com/">Slack</a> is the single best company embodiment of the focus/simplicity paradigm. Others take note.</p><p><strong><em>Hack the onboarding flow: </em></strong>It doesn’t matter how beautiful or utilitarian your product is if no one ever gets around to using it. Developers are a fickle bunch with seemingly infinite alternatives to your offering of paid tools, open source projects and self-built hacks. You generally have one chance with them, and that chance lasts about 20 minutes (based on conversations with some of the <em>least</em> ADHD-ridden devs I know).</p><p>On-boarding should emphasize and reinforce the value prop that drove the user to your product in the first place. Sign-up should be frictionless and deployment should be self-service to the point where the customer is up and running in minutes and, most importantly, getting value from your product a few moments right after. Avoid the empty room problem at all costs — even if the data or insight you provide early on has less direct customer value, it’s better than a customer looking at a blank screen.</p><p>Suggestion: read <a href="http://blog.newrelic.com/">New Relic’s early blog</a> posts. The company was fanatical about delivering value to devs from their APM solution within 5 minutes of signing up.</p><p><strong><em>Documentation, Documentation, Documentation: </em></strong>There’s nothing sexy or glamorous about documentation, but great docs can be a source of competitive differentiation. Look no further than <a href="http://stripe.com/">Stripe</a>, whose documentation is the stuff of legends (and a big reason why the company has grown as quickly as it has). Great documentation shows devs you care and it’s increasingly becoming table stakes, particularly if your product is technical or has an upfront integration burden. Given that, take the time to document from day 1 and don’t neglect those docs as your product offering expands.</p><p>An obvious corollary to the documentation point is around API cleanliness. Your API is a not adjunct to your product, it is an extension of the core; treat it as such.</p><p><strong><em>Content, Content, Content:</em></strong> Embrace content — it’s your opportunity to connect with users. Content doesn’t just mean static blog posts, but includes webinars, tutorials, analyst publications and reference architectures. Leverage content to showcase the integrations, use cases and features of your product. Digital Ocean does this masterfully. Just go check out their <a href="https://www.digitalocean.com/company/blog/">blog</a>.</p><p>Finally, make sure to quanitfy. Set a goal for TtV and benchmark against it. TtV’s vary widely across product segments and end-markets but study your comps and make sure you’re at least beating the pants off them.</p><p>An optimized TtV has positive ramifications throughout the organization ranging from freeing up support engineers to work on product to enabling a tightening of sales and marketing spend up and down the funnel. Ultimately, a short TtV drives all those other metrics folks seem to care so much about like MRR, LTV, CAC, Churn, etc.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=40815bd16196" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lenny-for-your-thoughts/the-most-important-saas-metric-nobody-talks-about-time-to-value-ttv-40815bd16196">The Most Important SaaS Metric Nobody Talks About: Time-to-Value (‘TtV’)</a> was originally published in <a href="https://medium.com/lenny-for-your-thoughts">Lenny for your Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Warehouse Computing and the Evolution of the Datacenter: A Layman’s Guide]]></title>
            <link>https://medium.com/lenny-for-your-thoughts/warehouse-computing-and-the-evolution-of-the-datacenter-a-layman-s-guide-a1b5a142e1bd?source=rss----4c96f577453e---4</link>
            <guid isPermaLink="false">https://medium.com/p/a1b5a142e1bd</guid>
            <category><![CDATA[warehouse-computing]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[containers]]></category>
            <dc:creator><![CDATA[Lenny Pruss]]></dc:creator>
            <pubDate>Fri, 01 Dec 2017 19:14:01 GMT</pubDate>
            <atom:updated>2017-12-01T19:14:22.541Z</atom:updated>
            <content:encoded><![CDATA[<p>You may not have noticed, but we’re in the midst of another massive platform shift in enterprise computing. We can debate chicken or egg, but I believe this most recent transformation is being driven primarily by requirements placed on modern applications; requirements that are the result of the on-demand, always-on computing paradigm predicated by cloud and mobile. Simply, applications need to be scalable, available and performant enough to reach millions, if not billions, of connected devices and end-users. Infrastructure must mirror these specifications, in kind.</p><p>Historically, systems design has ebbed and flowed between periods of aggregation (centralized) and disaggregation (distributed) of compute resources. The most recent evolution, from client/server to virtualized, cloud infrastructure was driven largely by a desire to contain costs and consolidate IT around standards (x86 instruction set, Windows and Linux) form factors (first blade servers, then VMs) and physical locations (emergence of sprawling datacenters and giant cloud vendors). Now we’re seeing the pendulum swing back. Why?</p><p>A strong first principle is the notion that infrastructure is beholden to the application. Today, many applications are being built as large-scale distributed systems, composed of dozens (or even thousands) of services running across many physical and virtual machines and often across multiple datacenters. In this paradigm, virtualization — which really dealt with the problem of low physical server utilization — doesn’t make much sense. In a highly distributed, service-oriented world, VMs come with too much overhead (read more on this<a href="http://devops.com/blogs/devops-toolbox/docker-vs-vms/"> here</a>). Instead of slicing and dicing compute, network and storage, the better solution becomes to aggregate all machines and present them to the application as a pool of programmable resources with hardware-agnostic software that manages isolation, resource allocation, scheduling, orchestration etc. In this world, the datacenter becomes one giant, warehouse computer controlled by a software brain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EEGuOMke1zM6wbmQVxnMpA.png" /></figure><p>However, the fact of the matter is that building, deploying and maintaining distributed applications is a highly technical feat. It requires a rethinking of the way applications treat and interact with other applications, databases, storage and network. Moreover, it requires a new toolkit that is central to solving the coordination and orchestration challenges of running systems that span across multiple machines, datacenters and time zones. To help understand what’s taking place, let’s deconstruct this new stack and, along the way, define some other key terms. Note that this is in no way a static, absolute taxonomy, but rather a simplified way to understand the layers that make up today’s application stack.</p><p><strong><em>Physical Infrastructure</em></strong> — Actual servers, switches, routers and storage arrays that occupy the datacenter. This area was dominated by legacy OEMs (EMC, Cisco, HP, IBM, Dell) who are now giving way to low-cost ‘<a href="https://www.ventureoutsource.com/contract-manufacturing/focus-odm-quanta-it-shift-cloud-infrastructure-leaving-dell-hp-traditional">whitebox’</a> ODMs.</p><p><em>Vendors/Products: </em><a href="http://www.quantatw.com/Quanta/english/">Quanta Computer</a>, <a href="http://www.supermicro.com/index_home.cfm">SuperMicro</a>, <a href="http://www.wistron.com/">Wistron</a></p><p><strong><em>Virtualized Infrastructure</em></strong> — Emulated physical compute, network and storage resources that are the basis for cloud-based architectures. The enabling technology here is the hypervisor which sits on top bare metal infrastructure and creates virtual clones of the server (or switch or storage array) each complete with a full OS with its own memory management, device drivers, daemons, etc.</p><p><em>Vendors/Products: </em><a href="https://aws.amazon.com/">Amazon Web Services</a>, <a href="https://cloud.google.com/">Google Cloud Platform</a>, <a href="https://azure.microsoft.com/en-us/">Microsoft Azure</a>, <a href="http://www.vmware.com/">VMware</a>, <a href="https://www.openstack.org/">OpenStack</a></p><p><strong><em>Operating System </em></strong>— Often stripped down version of host or guest OS that sits atop a virtual or physical host. The rise of Linux has been a key catalyst for the commoditization the OS and physical infrastructure, further decoupling applications from hardware. Microsoft with <a href="http://www.microsoft.com/en-us/server-cloud/products/windows-server-2012-r2/default.aspx">Windows Server</a> is still a dominant player in traditional enterprise.</p><p><em>Vendors/Products: </em><a href="https://coreos.com/">CoreOS</a>, <a href="http://www.projectatomic.io/">Project Atomic</a> (Red Hat), <a href="https://developer.ubuntu.com/en/snappy/">Snappy</a> (Ubuntu), <a href="http://rancher.com/rancher-os/">RancherOS</a>, <a href="http://blogs.technet.com/b/windowsserver/archive/2015/04/08/microsoft-announces-nano-server-for-modern-apps-and-cloud.aspx">Windows Nano Server</a></p><p><strong><em>Container Engine </em></strong>— This is where it starts to get interesting so let’s spend a little more time here. Linux containers offer a form of <a href="http://en.wikipedia.org/wiki/Operating-system-level_virtualization">operating system-level virtualization</a>, where the kernel of an OS allows for multiple user space instances. More simply, if hypervisor-based virtualization abstracted physical resources to create multiple server clones each with their own OS, the type of virtualization enabled by containers is a higher level abstraction of the OS, allowing appropriate levels of resource utilization and isolation to run multiple applications on a single kernel. The beauty of containers lies in the idea of “code once, run anywhere.” A container holds the application logic and all of its dependencies, running as an isolated process. What’s special about this is it ultimately doesn’t matter what’s inside the container (files, frameworks, dependences); it will still execute the same way in any environment — from laptop, to testing, to production across any cloud, at least theoretically. This enables application portability, which, in turn, commoditizes cloud infrastructure altogether.</p><p>Docker has become synonymous with containerization by making <a href="https://linuxcontainers.org/">Linux Containers (LXC)</a> user-friendly. The important thing to note is that container technology is made up of two fundamental components: the runtime or container engine and the container image format. The runtime is effectively a high-level API that runs processes and manages isolation. The image format is a specification for a standard composable unit for containers. In recent months we’ve seen <a href="https://coreos.com/blog/rocket/">several container runtimes and specs come to market</a> which has caused a <a href="http://lennypruss.co/post/104256400823/the-container-wars-have-started-and-we-should-be">stir</a>. I’m sure we’ll continue to see more.</p><p><em>Vendors/Products: </em><a href="https://www.docker.com/docker-engine">Docker Engine</a>, <a href="https://coreos.com/rkt/docs/latest/">CoreOS rkt</a>, <a href="https://www.opencontainers.org/">Open Container Initiative</a></p><p><strong><em>Service Discovery</em></strong> — Service discovery tools manage how processes and services in a cluster can find and talk to one another. This becomes increasingly important as application are run as collections of highly distributed disparate services. DNS can be used as solution here but suffers at scale, so many have no defaulted to building on top of highly consistent key-value storess.</p><p><em>Vendors/Products: </em><a href="https://coreos.com/etcd/">etcd</a> (CoreOS), <a href="https://www.consul.io/">Consul</a> (HashiCorp), <a href="https://zookeeper.apache.org/">Zookeeper</a> (Apache)</p><p><strong><em>Scheduling &amp; Orchestration</em></strong> — Schedulers interface with the resources of the cluster and are responsible for providing a consistent way to intelligently place tasks based on those resources. Additional tools in this area are responsible to defining and declaring infrastructure which will run tasks.</p><p><em>Vendors/Products: </em><a href="http://kubernetes.io/">Kubernetes</a>, <a href="http://mesos.apache.org/">Mesos</a> (<a href="https://medium.com/p/a1b5a142e1bd/mesosphere.com">Mesosphere</a>), <a href="https://www.serfdom.io/">Serf</a> + <a href="https://www.terraform.io/">Terraform</a> (Hashicorp), <a href="https://www.docker.com/docker-machine">Machine</a> + <a href="https://www.docker.com/docker-swarm">Compose</a> + <a href="https://www.docker.com/docker-compose">Swarm</a> (Docker)</p><p><strong><em>Workflow, Monitoring &amp; Management </em></strong>— Tools that automate the deployment lifecycle and management of applications and infrastructure. What some refer to as the management plane, these tools enables devs sysadmins to deploy and maintain applications across computer clusters. This area is largely greenfield as tools are being adapted to work with containers, not just VMs or physical nodes, across distributed environments. Products in this area include everything from automation and congif management frameworks, deployment pipelines to out-of-the-box PaaSs.</p><p><em>Vendors/Products: </em><a href="http://www.chef.com/">Chef</a>, <a href="http://www.puppetlabs.com/">Puppet</a>, <a href="http://www.ansible.com/">Ansible</a>, <a href="http://www.cloudfoundry.org/">CloudFoundry</a>, <a href="http://www.flynn.io/">Flynn</a>, <a href="http://www.circleci.com/">CircleCI</a>, <a href="http://www.travis-ci.org/">TravisCI</a>, <a href="http://www.gliderlabs.com/">Glider Labs</a>, <a href="http://www.signalfx.com/">SignalFx</a>, <a href="http://www.sysdigcloud.com/">SysDig</a> and dozens more.</p><p>A few other helpful definitions:</p><p><strong><em>Distributed System</em></strong> — A computing system consisting of a collection of autonomous nodes connected through a network and software/middleware which enables nodes to coordinate tasks and share resources of the entire system. The principle of distributed computing has been around for decades but only recently has it entered into mainstream IT as traditional software architecture has been pushed to its limits at Web scale. Perhaps the best known example is<a href="http://en.wikipedia.org/wiki/Apache_Hadoop"> Apache Hadoop</a>, an open-source data storage and processing framework where jobs are split and run across multiple commodity servers.</p><p><strong><em>Microservices</em></strong> — Microservice architecture is a way of designing software applications as sets of modular, self-contained, deployable services. Whereas historically applications would be split into client-side, server-side/logic and database, the idea with microservices is to develop each application as a suite of smaller, modular services each running its own process with a minimal amount of centralized management. Microservices architecture is appealing because it enables greater agility (entire applications don’t need be taken down during change cycles), speed-to-market and code manageability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*IvNSr2FFvaWDXSgjwq7hJg.png" /></figure><p><em>(Source: </em><a href="http://martinfowler.com/"><em>http://martinfowler.com</em></a><em>)</em></p><p>The application stack is an ever-evolving, dynamic organism. Ultimately, whether it’s microservices, distributed systems, or containers, the changes we’re seeing at both the code and infrastructure level are about one thing: delivering better, more scalable software faster and cheaper. As a result, today we find ourselves at the outset of, what I’ll call, the warehouse computing era, defined by cheap, commodity infrastructure presented to the application as a pool of dynamically programmable resources with intelligent, hardware-agnostic software as the control plane operating at n-scale.</p><p>To me, though, this is still an incremental step. The world of IT I envision is one where code is written once and is executed anywhere, automatically at scale, irrespective of the underlying cloud, OS, container engine, orchestrator, scheduler, etc. In this world, ops ceases to be an IT function and becomes a product within, or even feature of, the underlying stack. This world is several years away, and before we get there I can promise the tech stack is going to get a lot more convoluted before it radically simplifies. Either way, it’ll be fun to watch.</p><p><em>Notes: two other fantastic overviews of the modern stack are from Joe Beda </em><a href="http://www.eightypercent.net/post/layers-in-the-stack.html"><em>here</em></a><em> and the team at CoreOS </em><a href="https://coreos.com/blog/cluster-osi-model/"><em>here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1b5a142e1bd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lenny-for-your-thoughts/warehouse-computing-and-the-evolution-of-the-datacenter-a-layman-s-guide-a1b5a142e1bd">Warehouse Computing and the Evolution of the Datacenter: A Layman’s Guide</a> was originally published in <a href="https://medium.com/lenny-for-your-thoughts">Lenny for your Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Case for Microservices in the Enterprise]]></title>
            <link>https://medium.com/lenny-for-your-thoughts/the-case-for-microservices-in-the-enterprise-eab0eba9339?source=rss----4c96f577453e---4</link>
            <guid isPermaLink="false">https://medium.com/p/eab0eba9339</guid>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[enterprise]]></category>
            <category><![CDATA[perspective]]></category>
            <dc:creator><![CDATA[Lenny Pruss]]></dc:creator>
            <pubDate>Fri, 01 Dec 2017 19:13:31 GMT</pubDate>
            <atom:updated>2016-07-07T04:14:13.889Z</atom:updated>
            <content:encoded><![CDATA[<p>Since the last <a href="https://medium.com/@lennypruss/warehouse-computing-and-the-evolution-of-the-datacenter-a-layman-s-guide-a1b5a142e1bd">post</a> exploring the platform shift happening in today’s datacenter, the question I’ve been asked most often is, “sure, microservices, distributed architectures and containerization might make sense for the Google’s and Facebook’s of the world, but what about everyone else who doesn’t operate at Web scale?”</p><p>It’s true that the never-before-seen scale requirements thrust upon this generation’s consumer Internet companies necessitated a redesign of applications and their underlying systems, but scale is only part of the explanation. Rather, the wholesale changes seen at the infrastructure and code levels and across the software development lifecycle were born out of the fundamental desire to win, which ultimately comes down to delivering the best software to millions (or billions) of end-users fastest.</p><p>Scalability is top-of-mind, but just as important is creating organizational and software development structures that support innovation, agility and resilience. After all, I would argue that Facebook became Facebook because Zuck was maniacal about 1) maintaining hacker culture to buoy innovation which enabled the company to bring superior software to market faster than the competition and 2) eliminating downtime which he knew would be a growth killer. Without this focus on agility and resilience, Facebook’s ability to scale would be moot.</p><p>As enterprise IT has been consumerized, the lessons learned by the IT pros at places like Twitter and AirBnB have made their way to the Fortune 2000. And while enterprise apps don’t necessarily need to scale to even hundreds of thousands of users, business agility and risk mitigation are always top-of-mind strategic initiatives for CIOs. It follows that as every organization <a href="http://www.wsj.com/articles/SB10001424053111903480904576512250915629460">becomes a software organization</a>, competitive advantage will be characterized by companies’ ability to innovate, bring product to market faster and navigate risk.</p><p>So, how and why does this relate to the adoption microservices in the enterprise?</p><p>To level set, microservices implies an architectural choice to build and deploy applications as suites of discreet, modular services, each running its own process with a minimal amount of centralized management. Microservices encourage devs to decouple software into smaller, functional components with the expectation that they fail but don’t bring down the entire app. This, at least in theory, results in applications that are highly available, faster to build and easier to maintain. And consequently, adopting this architectural paradigm enables organizations of all sizes to innovate faster and mitigate risk. To fully appreciate this, it’s helpful understand how enterprise applications have been traditionally built and deployed and why and how this has evolved.</p><p><strong><em>The Challenge of the Monolith</em></strong></p><p>Enterprise app architecture hasn’t fundamentally changed for decades. Most apps are built using the three-tier model which became the dominant methodology in the client/server era. The idea is to split applications into independent, functional code bases consisting of the front-end (presentation tier), the back-end (logic tier) and data storage (data tier). See below for more details:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/890/0*HyQa42oBlYvP4low.png" /></figure><p><em>(Source: </em><a href="http://en.wikipedia.org/wiki/Multitier_architecture"><em>Wikipedia</em></a><em>)</em></p><p>However, there’s a common saying that goes something like, “every successful application is an architectural nightmare.” Problems arise when systems become too big and unwieldy. The reason being that as the application grows and features, integrations, etc. are added, it’s not uncommon for the code base to balloon to millions of lines of code.</p><p>There’s nothing inherently flawed with this; far from it. However, in a today’s world where scalability is table stakes and new releases are expected weekly or daily, managing these giant monoliths becomes a…nightmare. Any change, no matter how tiny, to any module requires rebuilding and testing the entire application. This, in turn, creates downtime, which we know is a killer. Moreover, because the functional components of the application are packaged together as a single unit, the only way to respond to changing levels in user demand is to scale the entire application; another giant headache.</p><p>Enter microservices…</p><p><strong><em>The Promise of Microservices</em></strong></p><p>The concept of building applications as series of composable, modular services is nothing new, dating back as far as the <a href="http://en.wikipedia.org/wiki/Unix_philosophy">first UNIX operating systems</a>. However, two more recent phenomena explain the uptick in adoption.</p><p>First is the ascension of open source software and the corresponding comfort of devs integrating external libraries and APIs into their applications. Second is the rise of containers — namely Docker — which offer a light-weight form of virtualization making applications fast and portable across infrastructure. The beauty of containers lies in this portability and the idea of “code once, run anywhere.” Because containers hold the application logic and all of its dependencies, running as an isolated process, they execute the same in any environment. This creates parity between dev and production, and enables developers to confidently break up apps into discreet chunks knowing they’ll run the same from their terminal to test to production. Suffice to say, containers have been a key enabler of microservices adoption.</p><p>You can see from the chart below that interest in microservices has grown in lock-step with interest in containers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3NrZxOykd9B5ybiz.png" /></figure><p>So what are the actual benefits of microservices architecture?</p><p>I had the opportunity to visit with <a href="https://twitter.com/mbryzek">Mike Bryzek</a>, co-founder and CTO of Gilt. Mike and his team are one of the most forward-looking technical organizations in the world, let alone New York. They were early adopters of <a href="http://en.wikipedia.org/wiki/Continuous_delivery">continuous delivery</a> methods and were successfully using Docker containers in production almost a year before Docker released v1.0. Today, Gilt’s platform is composed of over 400 unique applications, spanning the gamut from pure RESTful APIs to full stack databases and applications.</p><p>The primary goal of this massive technical transformation was to become a product-centric, developer-driven organization. To do so meant to enable individual tech teams across Gilt to drive innovation as quickly as possible, providing isolation for each team which, in turn, enabled safe iteration. Further, Mike characterized the shift to microservices as enabling three organizational initiatives:</p><p><strong><em>1. Growth</em></strong> — Innovation drives growth; organizations should strive to maximize opportunities to innovate. Microservices enabled Gilt to create self-contained teams that are responsible for their discreet application. Test and QA are performed within each team who then also determines release cycles, thereby owning the end-to-end product experience. This sense of ownership, in turn, drives quicker decision making and higher levels of innovation. Finally, empowering developers has proven to be a key selling point in attracting top technical talent.</p><p><strong><em>2. Agility</em></strong> — Gilt’s platform is composed of 400+ independent services, implying the organization can release and respond to bugs and feature requests faster.</p><p><strong><em>3. Risk</em></strong> — Gilt characterizes the expected cost of risk as follows:</p><p><em>R = Probability(bad event) * Cost(bad event) * Duration(bad event)</em> where bad event means anything degrading the customer experience. Microservices, if designed properly, provide significant isolation. As a result applications are built such that any and all dependencies between services are remote with the expectation that dependencies will fail. Whereas in a monolith a bug can bring down the whole app (“cascading failure”), in a microservices architecture only the compromised service goes down. As a result “bad events” are not so bad, so risk “<em>R” </em>is minimized.</p><p>There are advantages to adopting microservices in your organization that go far beyond scale, but let’s be clear: <a href="http://highscalability.com/blog/2014/4/8/microservices-not-a-free-lunch.html">microservices are not a panacea</a> for all that ails your software org and come with added complexity. Instead of managing across three or four tiers and, you’ll have dozens or hundreds of disparate services to build, test, deploy and run, likely in polyglot languages and environments. This creates significant operational and technical overhead.</p><p>Microservices represents not only a shift at the code and infrastructure levels of how software is designed and deployed, but also an organizational shift in how software development pipelines are constructed and managed. Therefore we’re likely to see not only a new set of tools to manage applications through dev, test and production, but also a new organizational tool kit for managing people and processes. This trend promises to produce dozens, if not hundreds, of exciting new companies.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eab0eba9339" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lenny-for-your-thoughts/the-case-for-microservices-in-the-enterprise-eab0eba9339">The Case for Microservices in the Enterprise</a> was originally published in <a href="https://medium.com/lenny-for-your-thoughts">Lenny for your Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Containers and the Search for the Killer App]]></title>
            <link>https://medium.com/lenny-for-your-thoughts/containers-and-the-search-for-the-killer-app-8b45d4d9ad5b?source=rss----4c96f577453e---4</link>
            <guid isPermaLink="false">https://medium.com/p/8b45d4d9ad5b</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[trends]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[perspective]]></category>
            <dc:creator><![CDATA[Lenny Pruss]]></dc:creator>
            <pubDate>Fri, 01 Dec 2017 19:12:55 GMT</pubDate>
            <atom:updated>2016-07-07T04:12:26.227Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/661/0*o6_S_loXAH_1dmqo.png" /></figure><p>VisiCalc for early PCs. E-mail for the Internet. SMS for mobile. Every major tech platform we’ve seen has had the benefit of a “killer application” that transformed it from “toy” or “cool project” into an indispensable, mainstream product.</p><p>Now that that we’re in the midst of what looks to be another <a href="https://medium.com/@lennypruss/warehouse-computing-and-the-evolution-of-the-datacenter-a-layman-s-guide-a1b5a142e1bd">major platform shift in the datacenter</a> — this time with the layer of abstraction moving from physical infrastructure via the hypervisor to the OS via containerization — talk has centered around Linux containers and whether they represent a paradigm shift in how we build and deploy applications or if they are simply another instrument in the DevOps toolkit.</p><p>The relevant analog for mapping out the fate of containerization seems to be virtualization. Charting <a href="http://vmware.com/">VMware</a>’s history provides a hint of how container adoption and ecosystem development may unfold, but it’s far from a perfect corollary.</p><p>In 1999, VMware released Workstation which let developers run multiple virtual machines with different operating systems locally. This solved an acute developer pain around building applications that would work across different OS’s and environments. A couple years later the company entered the server market with ESX and vMotion which enabled live migration; a fancy way of saying you could move running VMs between physical hosts without taking the whole application down. The VMware toolchain quickly spread through dev/test as developers could now build and test applications for different environments and then deploy them with a few clicks confident they wouldn’t break production (assuming proper config files were installed; hence the rise of config management tools like Chef, Puppet, etc.). In addition to this grass-roots, bottoms-up adoption, virtualization benefited from CIO-led, top-down initiatives to eliminate IT sprawl, improve server utilization and consolidate datacenters. The result, depending on who you ask today, is that anywhere from 75–90% of x86 workloads are virtualized.</p><p>Hardware virtualization, then, literally digitized the analog task of racking servers. It represented a step-function improvement over how IT could be provisioned and administered and how applications could be tested and deployed.</p><p>Now we’re seeing similar developer-led adoption of containerization, and sure enough there are myriad reasons why adopting Linux containers makes sense: from enabling application portability across compute and cloud infrastructures, to streamlining your deployment pipeline to liberating your organization from the VMware tax. <em>But</em> as we sit here today, many (including myself) contend that containers don’t represent as radical a step-function improvement over the tools used to solve similar problems as VMs did in the early 2000s. Nor is there a similar top-down, CTO-/CIO-led initiative to catalyze adoption. Consequently, what we’re looking for is the killer application that unlocks the value of containers for the mass-market.</p><p>What might those killer apps be? Here are three likely candidates:</p><p><strong><em>“Dropbox-ized” dev environments</em></strong> — One of the most nagging engineering pains is provisioning and replicating developer environments across the org and then maintaining parity between those environments with test and production. Containers offer a way to encapsulate code with all of its dependencies allowing it to run the same irrespective of underlying infrastructure. Because containers share the kernel user space, they offer a more lightweight alternative to VM-based solutions like <a href="https://www.vagrantup.com/">Vagrant</a>, thereby letting devs code/build/test every few minutes without the virtualization overhead. Consequently, orgs can create isolated and repeatable dev environments that are synced through the development lifecycle without resorting to cloud IDEs which have been the bane of many devs’ existences.</p><p><strong><em>Continuous deployment</em></strong> — As every company becomes a software company at its core, faster release cycles become a source of competitive advantage. This was highlighted in the recent <a href="https://puppetlabs.com/2015-devops-report">Puppet Labs State of DevOps</a> report, where it was revealed that “high performing IT organizations” deploy code 30x faster and have 200x shorter lead times leading to 60x fewer failures than their “low-performing” peers. It’s no surprise, then, that organizations are embracing continuous delivery practices in earnest. Containers, because of their inherent portability, are an enabler of this software deployment model. Instead of complex scripting to package and deploy application services and infrastructure, with containers scripts shrink to a couple lines to push or pull the relevant image to the right endpoint server and CI/CD becomes radically simplified.</p><p><strong><em>Microservices</em></strong> — Microservices architecture refers to a development practice of building an application as a suite of modular, self-contained services each running its own process with a minimal amount of centralized management. Microservices itself is a <a href="http://lennypruss.co/post/115764339348/the-case-for-microservices-in-the-enterprise">means not an end</a>, enabling greater agility (entire applications don’t need be taken down during change cycles), speed-to-market and code manageability. Containers, offering lightweight isolation, are the key enabling technology for this development paradigm.</p><p>Ultimately, containerization allows companies of all sizes to <strong><em>write better software faster</em></strong>. But as with any platform shift, there is a learning curve and broad adoption is a function of ecosystem maturity. We’re just now beginning to see the emergence of best practices and standards via organizations like the <a href="https://www.opencontainers.org/">Open Container Initiative</a> and the <a href="https://cncf.io/">Cloud Native Computing Foundation</a>. The next step is for a hardened management toolchain to emerge which will allow devs and companies to begin building out powerful use cases. And it’s with those applications that we will start to unlock the power of container technology for the masses.</p><p><em>This article first appeared on ContainerJournal.com and can be found </em><a href="http://containerjournal.com/2015/07/30/containers-and-the-search-for-the-killer-app/"><em>here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8b45d4d9ad5b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lenny-for-your-thoughts/containers-and-the-search-for-the-killer-app-8b45d4d9ad5b">Containers and the Search for the Killer App</a> was originally published in <a href="https://medium.com/lenny-for-your-thoughts">Lenny for your Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Containers and the Chasm: A Look at Container Adoption]]></title>
            <link>https://medium.com/lenny-for-your-thoughts/containers-and-the-chasm-a-look-at-the-state-of-container-adoption-a4de09853752?source=rss----4c96f577453e---4</link>
            <guid isPermaLink="false">https://medium.com/p/a4de09853752</guid>
            <category><![CDATA[trends]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Lenny Pruss]]></dc:creator>
            <pubDate>Fri, 01 Dec 2017 19:11:23 GMT</pubDate>
            <atom:updated>2016-07-07T04:13:19.263Z</atom:updated>
            <content:encoded><![CDATA[<p>Geoffrey Moore’s technology adoption lifecycle is gospel for tech marketers. The model describes the path of diffusion for discontinuous innovations and explains how ecosystems emerge and coalesce around IT winners.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zN9ClhGzFc4bZ8Pd8Q21Tg.png" /></figure><p>Moore and his work have been top of mind the last couple years now as we’ve observed the rise of and hype around Linux containers.</p><p>Containers are the next evolutionary leap forward from hypervisor-based hardware virtualization, offering a way to package an application with a complete filesystem that holds everything it needs to run: code, runtime, system tools and libraries. Containers are smaller, faster, more portable and more developer-friendly than their virtual machine predecessors. In that, containerization represents a paradigm shift in how systems and applications are built, deployed and managed.</p><p>In the tech sector, paradigm shift is a euphemism for opportunity, and, appropriately, we’ve seen a flood of companies come to market with their flavors of tools and platforms to ultimately enable organizations to run container-based, <a href="https://medium.com/@lennypruss/the-cloud-native-ecosystem-f0484fb3d57f">cloud-native</a> applications.</p><p>The rapid onset of this innovation cycle has been exacerbated by a trend toward faster release times. VMware got buyers comfortable with a new vSphere release every year. Then the OpenStack Foundation promised releases every six months. With Docker, CoreOS and others we’re seeing releases every three months, if not faster, as each vies to become the standards bearer (if only judged by press mentions or Github stars).</p><p>Consequently, lost in this shuffle have been customers who are struggling to keep up.</p><p>To assess the state of container adoption, it’s helpful to evoke Moore’s model. Let’s take a look through that lens:</p><p><em>Innovators</em> are “willing to take risks, have the highest social status, have financial liquidity, are social and have closest contact to scientific sources and interaction with other innovators. Their risk tolerance allows them to adopt technologies that may ultimately fail. Financial resources help absorb these failures.” These are the Googles and Twitters of the world who have been running containers as part of distributed systems architectures years before Docker was open sourced. These companies battle test approaches and provide blue prints for the broader market but operate at a scope and scale that is many years ahead of it.</p><p><em>Early adopters</em> are “individuals with the highest degree of opinion leadership among the adopter categories. Early adopters have a higher social status, financial liquidity, advanced education and are more socially forward than late adopters.” These ‘gear-heads,’ are the developers and infrastructure engineers who have been test-driving container technology because it’s the cool, new thing. These devs are evangelists and core open source contributors and are responsible for driving standards, best practices and use cases. Early adopters are gatekeepers for new technologies in organizations and drive bottoms-up adoption.</p><p>However, bottoms-up adoption will only take a new innovation so far, which brings us to Moore’s famous <em>chasm</em>. The chasm is a gap that exists between the first two adoption cohorts and the <em>early majority</em>, where buyers are described as “pragmatists in pain,” and adoption decisions are driven by business need.</p><p>The chasm is precisely where we stand today: developer interest continues to surge as <a href="https://www.opencontainers.org/">standards</a> and <a href="https://cncf.io/">best practices</a> are beginning to emerge, but the industry is still waiting on the <a href="/service/mailto:%20https://medium.com/@lennypruss/containers-and-the-search-for-the-killer-app-8b45d4d9ad5b">applications and business cases</a> which are requisite to drive more mainstream adoption.</p><p>Given that we’re at this critical inflection point, we urge companies competing in this market to take the pragmatic, customer-centric view. Ultimately, this all relates to a potential brewing problem in the formation of any new ecosystem or value chain: when the rate of innovation outpaces the rate of customer adoption companies fail.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4de09853752" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lenny-for-your-thoughts/containers-and-the-chasm-a-look-at-the-state-of-container-adoption-a4de09853752">Containers and the Chasm: A Look at Container Adoption</a> was originally published in <a href="https://medium.com/lenny-for-your-thoughts">Lenny for your Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Developer Tools Gold Rush]]></title>
            <link>https://medium.com/lenny-for-your-thoughts/the-developer-tools-gold-rush-a0bc490ada88?source=rss----4c96f577453e---4</link>
            <guid isPermaLink="false">https://medium.com/p/a0bc490ada88</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[perspective]]></category>
            <category><![CDATA[trends]]></category>
            <dc:creator><![CDATA[Lenny Pruss]]></dc:creator>
            <pubDate>Fri, 01 Dec 2017 19:10:39 GMT</pubDate>
            <atom:updated>2016-07-07T04:11:22.867Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/448/1*0avGNbnIvOyBOlnbuuY5Hw.jpeg" /></figure><p>“You can’t make money selling to developers.”</p><p>That was a common axiom that permeated the venture community as recently as a few years ago. But just in the last couple quarters, <a href="http://techcrunch.com/2015/07/29/github-raises-250m-series-b-round-to-take-risks/">GitHub</a>, <a href="http://techcrunch.com/2015/07/28/stripe-5-billion/">Stripe</a>, <a href="http://techcrunch.com/2015/07/29/twilio-closes-130m-series-e-round-led-by-fidelity-and-t-rowe-price/">Twilio</a> and <a href="http://fortune.com/2015/04/16/why-slack-just-raised-160-million-at-a-2-8-billion-valuation/">Slack</a> have all raised giant rounds valuing each company at least one billion dollars. <a href="http://www.mesosphere.com/">Mesosphere</a>, a company founded less than three years ago, is rumored to have been the target of a <a href="https://www.theinformation.com/Cloud-Giants-are-Eyeing-Mesosphere">buyout</a> with the purported price tag starting at one billion dollars. Meanwhile in the public markets, while the Twitters, Yelps, Etsys, of the world got pummeled, the likes of <a href="http://www.newrelic.com/">New Relic</a> and <a href="http://www.splunk.com/">Splunk</a> have gained or, at very least, held constant.</p><p>What’s changed? Why are companies that target developers suddenly the hottest ticket in town?</p><p>Most simply, the answer relates to the coming of age of the software economy. Over the last decade, we’ve seen an acceleration away from the old ways of doing business inherent to the post-Industrial economy towards the new modalities of a software-based one as the forces of open source, cloud and mobile have all but eviscerated barriers to adoption, distribution and innovation for information technology.</p><p>As more of our physical world becomes instantiated in digital bits, every aspect of the global industrial order is being remade — from how we <a href="http://blog.learningbyshipping.com/2013/08/20/continuous-productivity-new-tools-and-a-new-way-of-working-for-a-new-era/">work</a> and <a href="http://venturebeat.com/2015/07/12/these-9-trends-show-the-future-of-mobile-payments-and-banking/">transact</a> with one another to how we <a href="http://www.forbes.com/sites/bernardmarr/2015/04/21/how-big-data-is-changing-healthcare/">treat diseases</a> and <a href="http://www.theatlantic.com/technology/archive/2015/06/hacking-and-the-future-of-warfare/395723/">fight wars</a>. Fundamentally this implies that every organization in the world is in the midst of transforming in some way, shape or form into a software organization.</p><h3></h3><p></p><p>This isn’t news; this revolution has been top-of-mind for nearly <a href="http://www.wsj.com/articles/SB10001424053111903480904576512250915629460">five years now</a>, but only now are we witnessing the ramifications of a full-fledged transition to a software economy.</p><p>Chief among those, is that with technology now table stakes, the developer is the organization’s top <a href="https://medium.com/memory-leak/the-developer-driven-economy-how-the-developer-has-become-the-organization-s-most-influential-d74ed11207b">power broker</a>. Correspondingly, companies that win are characterized by their ability to write better software faster (hence the rise of <a href="http://venturebeat.com/2014/03/10/continuous-delivery/">continuous delivery</a> and <a href="http://www.forbes.com/sites/jasonbloomberg/2015/04/09/software-and-devops-are-eating-the-world/">DevOps</a> practices), and the tools that enable them to do so are inevitably gaining an increasing share of budget dollars. Combine this with an explosion in demand for those with technical skills — software developer positions are supposed to <a href="http://www.infoworld.com/article/2613549/it-jobs/software-developers-expected-to-see-the-highest-it-job-growth-come-2020.html">grow 22%</a> from 2012 to 2020 — and it’s no wonder why we’re in the midst of a dev tool awakening: more developers with increased organizational power wielding greater control over purchase decisions.</p><p>The data is telling. Since 2011, total dollars invested in developer-focused businesses has grown nearly 65% annually with the total eclipsing $2.3 billion in 2014. By all measures, that figure stands to be smashed again in 2015 — through Q3 this year, $2.1 billion has been invested in “dev tools” business vs. $1.8 billion in the same period last year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*Kg-Ufz1TQrmAwDbUP-tn-A.png" /><figcaption>Developer tools funding data through Sept. 30, 2015. (CBInsights and Redpoint Ventures data)</figcaption></figure><p>With regards to taxonomy, developer tools have always defied classical categorization and are becoming even more ambiguous to define as more and more of the physical world becomes expressed through binary. However, we broadly group dev tools into four distinct buckets:</p><p><em>Developer productivity</em> — Tools that help developers write and collaborate around code. Examples include language frameworks and libraries (<a href="https://golang.org/">Golang</a>, <a href="https://facebook.github.io/react/">React</a>), development environments (<a href="https://www.vagrantup.com/">Vagrant</a> / <a href="https://hashicorp.com/blog/otto.html">Otto</a>), source code management (<a href="http://www.github.com/">GitHub</a>), collaboration (<a href="http://www.slack.com/">Slack</a>, <a href="http://www.sourcegraph.com/">SourceGraph</a>) and project management platforms (<a href="https://www.atlassian.com/software/jira">Jira</a>, <a href="http://www.asana.com/">Asana</a>).</p><p><em>Software lifecycle management</em> — Tools that test, deploy, manage and monitor code across dev, test/QA and production environments. Examples include build automation (<a href="http://ant.apache.org/">Ant</a>, <a href="https://gradle.org/">Gradle</a>), continuous integration and delivery platforms (<a href="http://www.circleci.com/">CircleCI</a>, <a href="https://jenkins-ci.org/">Jenkins</a>), test and QA software (<a href="http://www.applause.com/">Applause</a>, <a href="http://www.rainforestqa.com/">RainforestQA</a>), application performance monitoring (<a href="http://www.newrelic.com/">New Relic</a>) and infrastructure monitoring (<a href="http://www.datadog.com/">Datadog</a>).</p><p><em>Infrastructure-as-code</em> — Emulated, programmable compute, storage and network resources responsible for executing logic and running and scaling applications. Examples include virtualized infrastructure (<a href="http://www.aws.amazon.com/">AWS</a>), databases (<a href="http://www.mongodb.com/">MongoDB</a>, <a href="http://www.cockroachlabs.com/">CockroachDB</a>), operating systems (<a href="http://www.coreos.com/">CoreOS</a>), container engines (<a href="http://www.docker.com/">Docker</a>), cluster management (<a href="http://www.mesosphere.com/">Mesosphere</a>, <a href="http://kubernetes.io/">Kubernetes</a>), configuration management (<a href="https://puppetlabs.com/">Puppet</a>, <a href="http://www.chef.io/">Chef</a>), and well as full-stack deployment and management platforms (<a href="https://www.cloudfoundry.org/">Cloud Foundry</a>).</p><p><em>Services-as-code</em> — Products and services that are instantiated in code and delivered via APIs and SDKs. Examples include communications (<a href="http://www.twilio.com/">Twilio</a>), payments (<a href="http://www.stripe.com/">Stripe</a>), business intelligence (<a href="http://www.segment.io/">Segment</a>) commerce (<a href="http://www.shopify.com/">Shopify</a>), mapping (<a href="http://www.mapbox.com/">Mapbox</a>), analytics (<a href="http://www.keen.io/">Keen.io</a>) and many others.</p><p>Correspondingly, in every one of those categories just in the last several years we’ve seen the emergence of multiple dominant companies, all of which have succeeded by winning the hearts and minds of the developer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/856/1*K0fyQw54d_ZefnMldLdwgw.png" /><figcaption>Developer tools ‘unicorns.’ (CBInsights and Redpoint Ventures data)</figcaption></figure><p>It stands to reason that as this new software economy matures, developers will only continue to grow in role and importance. It should come as no surprise, then, that we’re at the outset of a gold rush for the picks and shovels that will make those developers and the software they create better.</p><p><em>This post first appeared on </em><a href="http://techcrunch.com/2015/11/04/party-like-its-1849-the-developer-tools-gold-rush/#.xw8kv5:VDcr"><em>TechCrunch</em></a><em> on November 4, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a0bc490ada88" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lenny-for-your-thoughts/the-developer-tools-gold-rush-a0bc490ada88">The Developer Tools Gold Rush</a> was originally published in <a href="https://medium.com/lenny-for-your-thoughts">Lenny for your Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[So, You Want to Go Cloud Native? First Ask Why]]></title>
            <link>https://medium.com/lenny-for-your-thoughts/so-you-want-to-go-cloud-native-first-ask-why-79ba1b3ab8f0?source=rss----4c96f577453e---4</link>
            <guid isPermaLink="false">https://medium.com/p/79ba1b3ab8f0</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[perspective]]></category>
            <dc:creator><![CDATA[Lenny Pruss]]></dc:creator>
            <pubDate>Fri, 01 Dec 2017 19:10:02 GMT</pubDate>
            <atom:updated>2016-07-07T04:08:32.829Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EoSyHkO-zVwtFaTZ.jpg" /></figure><p><em>This post first appeared in </em><a href="http://www.thenewstack.com/"><em>The New Stack</em></a><em> on </em><a href="https://thenewstack.io/want-go-cloud-native-first-ask/"><em>February 5, 2016</em></a><em>.</em></p><p>Over the last couple years the term “cloud native” has entered the collective consciousness of those designing and building applications and the infrastructure that supports them. At its heart, cloud native refers to a software architecture paradigm tailored for the cloud. It calls that applications 1) employ containers as the atomic unit for packaging and deployment, 2) be autonomic, that is centrally orchestrated and dynamically scheduled, and 3) be microservices-oriented, that is be built as loosely-coupled, modular services each running an independent process, most often communicating with one another through HTTP via an API.</p><p>Dissecting those characteristics further implies that modern applications need be platform-independent (e.g. decoupled from physical and/or virtual resources to work equally well across cloud and compute substrates), highly elastic, highly available and easily maintainable.</p><p>By the sound of that, it holds that building cloud native applications is a no-brainer for every organization, whether they consider writing software business-critical or not. In practice, however, going cloud native — much like adopting DevOps — requires putting into place a broad set of new technologies and practices which meaningfully shift around overhead costs associated with writing, deploying and managing software. So before considering going cloud native, it’s imperative to understand the motivations for this architectural transformation, both technically and organizationally.</p><p>A good place to start is with Google, the poster child for this highly distributed, autonomic computing paradigm. Google has been running on containerized infrastructure for nearly a decade and manages resource allocation, scheduling, orchestration and deployment through a proprietary system called Borg. In a research paper released in 2015, <a href="http://static.googleusercontent.com/media/research.google.com/en/pubs/archive/43438.pdf"><em>Large-scale cluster management at Google with Borg</em></a>, Google elucidates its motivations:</p><blockquote>Borg provides three main benefits: it (1) hides the details of resource management and failure handling so its users can focus on application development instead; (2) operates with very high reliability and availability, and supports applications that do the same; and (3) lets us run workloads across tens of thousands of machines effectively.</blockquote><p>So Google’s rationale for going cloud-native is to achieve 1) agility, as defined by developer productivity and self-service, 2) fault-tolerance and 3) horizontal scalability. And while almost no organization has to operate at the massive scale of Google, every company in the world asks itself “how do I go faster” and “how do I minimize risk?”</p><p>Problems arise, however, when going cloud native becomes an end, not a means. While containers, autonomic scheduling and microservices-oriented design are all tools which can facilitate operational agility and reduce risk associated with shipping software, they are far from a panacea and involve shifting meaningful costs from dev to prod. Martin Fowler and others have termed this phenomenon the “<a href="http://martinfowler.com/bliki/MicroservicePremium.html">microservices premium</a>”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/397/1*mXPkxgog1bsNC-E_WqVVZw.png" /><figcaption>martinfowler.com</figcaption></figure><blockquote>The [cloud native] approach is all about handling a complex system, but in order to do so the approach introduces its own set of complexities. When you [adopt cloud native architectures] you have to work on automated deployment, monitoring, dealing with failure, eventual consistency, and other [complexities] that a distributed system introduces.</blockquote><p>The prevailing fallacy is to conflate using Docker as package format with the need to build an application as a complex distributed system from the get-go.</p><p>The first rule of the thumb is “if ain’t broke, don’t fix it,” so there’s no need for added complexity if your team is functioning at a high level, releases are on schedule and your app is resilient and scaling to meet the demand of users. Sustained high levels of developer productivity, continuous deployment and fault tolerant systems can be and are often achieved without so much as ever interacting with a Dockerfile (though it can radically simplify the development workflow). In fact, many of the most elegant delivery pipelines in high performance software organizations are AMI-based and deployed by Slackbots!</p><p>However, as your engineering organization balloons to 100+ devs, going cloud native — including stand up the entire distributed runtime — very well could begin to make sense. Just remember, all these decisions are tradeoffs, where complexity is merely shifted not reduced.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=79ba1b3ab8f0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lenny-for-your-thoughts/so-you-want-to-go-cloud-native-first-ask-why-79ba1b3ab8f0">So, You Want to Go Cloud Native? First Ask Why</a> was originally published in <a href="https://medium.com/lenny-for-your-thoughts">Lenny for your Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Googlization of IT: Three Google Papers Transforming Enterprise Infrastructure]]></title>
            <link>https://medium.com/lenny-for-your-thoughts/the-googlization-of-it-three-google-papers-transforming-enterprise-infrastructure-69ad975352e8?source=rss----4c96f577453e---4</link>
            <guid isPermaLink="false">https://medium.com/p/69ad975352e8</guid>
            <category><![CDATA[trends]]></category>
            <category><![CDATA[infrastructure]]></category>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[google]]></category>
            <dc:creator><![CDATA[Lenny Pruss]]></dc:creator>
            <pubDate>Fri, 01 Dec 2017 19:09:20 GMT</pubDate>
            <atom:updated>2016-07-07T04:08:19.710Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/771/1*IW6bAjERvz4STLppGzrKAA.png" /></figure><p>There’s a saying that permeates Silicon Valley that goes something like, “if you want to know how the rest of the world will run its infrastructure in 10 years, go look at what Google is doing today.” While this might be slight hyperbole, there’s no question that Google has already left an indelible imprint on traditional enterprise IT from <a href="http://research.google.com/archive/mapreduce.html">commoditizing data storage and processing</a> to ushering in the <a href="http://static.googleusercontent.com/media/research.google.com/en/archive/bigtable-osdi06.pdf">NoSQL era</a> to making popular the <a href="http://research.google.com/pubs/pub35290.html">warehouse-scale computing</a> paradigm that dominates Webscale outfits like Facebook, Twitter and Uber.</p><p>Looking out across datacenters today, there’s a massive shift taking place driven by the rise of decentralized applications (which in turn has been driven by the massive scale and performance requirements predicated by mobile and cloud). As companies of all sizes transform into software organizations, they are running into the same set of challenges around agility, scale and uptime while trying to rein in costs. Not coincidently, these were all challenges faced — and more-less solved — by Google as it came to dominate the Web.</p><p>So, with the <a href="https://medium.com/memory-leak/so-you-want-to-go-cloud-native-first-ask-why-79ba1b3ab8f0#.3x7vjlyw7">cloud-native transformation</a> in full swing, we can begin to understand and appreciate the changes taking place up and down the stack for the rest of the world by examining how Google has architected its compute and data tiers and how it handles monitoring and management. Three Google papers in particular highlight the emergent architectural paradigms we’re seeing today and the motivations behind their rapid adoption.</p><p><a href="http://research.google.com/pubs/pub43438.html"><strong><em>Large-scale cluster management at Google with Borg</em></strong></a> <em>— Verma et al. (Google) 2015</em></p><p>Google has been running on containerized infrastructure for nearly a decade and manages cluster resources, scheduling, orchestration and deployment through a proprietary system called Borg which provides three main benefits:</p><blockquote>“…it (1) hides the details of resource management and failure handling so its users can focus on application development instead; (2) operates with very high reliability and availability, and supports applications that do the same; and (3) lets us run workloads across tens of thousands of machines effectively.”</blockquote><p>Borg serves as the central nervous system for Google’s datacenters. Instead of standing up separate clusters for each workload or application — whether that be batch data processing jobs, stateful services or long-running services like Search or Gmail — Google devs deploy code to Borg which then distributes and schedules workloads and allocates the requisite CPU, memory, etc. resources. Borg enables Google to achieve greater levels of agility (through developer self-service and automation), fault tolerance, scalability and resource utilization — Borg is rumored to have saved Google the capex associated with the build out of at least two additional datacenters.</p><p>Today we’re seeing the adoption of several Borg-like distributed runtimes, with Apache <a href="http://mesos.apache.org/">Mesos</a>, Google’s / <a href="https://cncf.io/">CNCF</a>’s <a href="http://kubernetes.io/">Kubernetes</a> and <a href="https://www.docker.com/products/docker-swarm">Docker</a>’s <a href="https://www.docker.com/products/docker-swarm">Swarm</a> leading the way. These platforms promise to streamline deployment, schedule and orchestrate containerized services and create a similar cross-datacenter autonomic computing fabric that Google has been running on for years.</p><p><a href="http://static.googleusercontent.com/media/research.google.com/en/pubs/archive/39966.pdf"><strong><em>Spanner: Google’s Globally-Distributed Database</em></strong></a> <em>— Corbett et al. (Google) 2012</em></p><p>At Google, all services require distributed operation, must be highly available and handle machine failures transparently. It stands to reason that the stateful services backing these workloads are of proportional scale and also require distributed operation and must be similarly — if not more — resilient to outages.</p><p>Spanner is Google’s globally distributed, and synchronously-replicated database which backs nearly every application within Google. Spanner features horizontal scalability, automatic sharding and fault tolerance similar to its NoSQL predecessor BigTable. However, it’s Spanner’s consistent replication, support of transactional semantics, relational data model and SQL interface that sets it apart from many prevailing NoSQL data stores (DyanmoDB, Cassandra, Mongo, etc.).</p><p>The motivation for strong consistency and distributed transactions was increased developer productivity. Google’s learning with BigTable was that it’s ultimately easier for the database to handle transaction logic while devs can focus on optimizing performance at the application tier.</p><blockquote>“Finally, the lack of cross-row transactions in Bigtable led to frequent complaints…We believe it is better to have application programmers deal with performance problems due to overuse of transactions as bottlenecks arise, rather than always coding around the lack of transactions.”</blockquote><p>In the single-server, monolithic application or even a three-tier Web app, managing state was fairly straight forward. But now as apps become decentralized and decomposed into dozens or hundreds of services, stateful back-ends should be distributed and multi-tenant, in kind. Of course supporting a distributed, shared database requires a team of DBAs so more recently we’ve seen the emergence of solutions like <a href="https://aws.amazon.com/rds/aurora/">AWS Aurora</a>, a fully-managed scale-out RDBMS, and even more ambitious projects like <a href="http://www.cockroachlabs.com/">CockroachDB</a> (based on Google’s Spanner) which gives you out-of-the-box scalability and survivability with strong consistency, geo-replication and a SQL interface.</p><p><a href="http://research.google.com/pubs/pub36356.html"><strong><em>Dapper, a Large-Scale Distributed Systems Tracing Infrastructure</em></strong></a><strong><em> </em></strong><em>— Sigelman et al. (Google) 2010</em></p><p>With applications being built as complex distributed systems composed of dozens, hundreds or thousands of discreet services, debugging, performance tuning, introspection and monitoring become major organizational challenges. The operational complexity associated with decentralized applications — daily/hourly deploys, polyglot code bases, ephemeral compute, multi-tenant infrastructure with multiple layers of abstraction — necessitates a new monitoring paradigm.</p><p>It’s this complexity which motivated Google to create Dapper, a production distributed systems tracing infrastructure which provides…</p><blockquote>“…developers with information about the behavior of complex distributed systems…When systems involve not just dozens of subsystems but dozens of engineering teams, even [the] best and most experienced engineers routinely guess wrong about the root cause of poor end-to-end performance. In such situations, Dapper can furnish much-needed facts and is able to answer many important performance questions conclusively.”</blockquote><p>The power of tracing lies in the ability introspect the entire data path — from client request to system call — at a given moment in time. In traditional monolithic systems debugging, monitoring latency, etc. are well understood, but once a production system contends with concurrency or divides into many services, these crucial (and formerly easy) tasks become complex. Given that, we’re now seeing a push for the emergence of tracing standards with the <a href="http://opentracing.io/">OpenTracing Project</a> that will buoy the adoption of open source tracing projects like <a href="http://www.zipkin.io/">Zipkin</a> and <a href="http://incubator.apache.org/projects/htrace.html">HTrace</a> as well as powerful platforms like <a href="http://www.lightstep.com/">LightStep</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69ad975352e8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/lenny-for-your-thoughts/the-googlization-of-it-three-google-papers-transforming-enterprise-infrastructure-69ad975352e8">The Googlization of IT: Three Google Papers Transforming Enterprise Infrastructure</a> was originally published in <a href="https://medium.com/lenny-for-your-thoughts">Lenny for your Thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>