<?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[Stories by David Gonzalez on Medium]]></title>
        <description><![CDATA[Stories by David Gonzalez on Medium]]></description>
        <link>https://medium.com/@daveops?source=rss-f0609ba10c37------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*mnmuniDaTtXciEM8JQCCxQ.jpeg</url>
            <title>Stories by David Gonzalez on Medium</title>
            <link>https://medium.com/@daveops?source=rss-f0609ba10c37------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:02:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@daveops/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What is the fuss with __proto__ in Node?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">So, lately, I have been looking into some internals of Node (and JavaScript in general) and I came across an interesting security problem&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@daveops/what-is-the-fuss-with-proto-in-node-caa998182f12?source=rss-f0609ba10c37------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@daveops/what-is-the-fuss-with-proto-in-node-caa998182f12?source=rss-f0609ba10c37------2</link>
            <guid isPermaLink="false">https://medium.com/p/caa998182f12</guid>
            <dc:creator><![CDATA[David Gonzalez]]></dc:creator>
            <pubDate>Wed, 30 Dec 2020 00:02:39 GMT</pubDate>
            <atom:updated>2020-12-30T00:02:39.744Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Kubernetes from A to Z: Intro]]></title>
            <link>https://medium.com/@daveops/kubernetes-from-a-to-z-intro-ad425051cf59?source=rss-f0609ba10c37------2</link>
            <guid isPermaLink="false">https://medium.com/p/ad425051cf59</guid>
            <category><![CDATA[node]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[David Gonzalez]]></dc:creator>
            <pubDate>Sat, 29 Oct 2016 18:10:40 GMT</pubDate>
            <atom:updated>2016-10-29T18:10:40.727Z</atom:updated>
            <content:encoded><![CDATA[<p>So, microservices are now a thing. In fact, microservices are a big thing and everybody is moving towards them. The problem with microservices is something that usually gets overlooked but it is one of the key points to succeed: <strong>automation</strong>.</p><p>Automation is as important in microservices as it is the technology choice when developing them. Up to now, the automation was not focused on microservices: <strong>Chef</strong>, <strong>Puppet</strong> and <strong>Ansible</strong> are great but they don’t easily allow you to deploy new versions of your software: they are designed to provision infrastructure.</p><p>Then Docker came into play but still there are some issues around running docker in production:</p><ul><li>Your application usually spans across different servers.</li><li>The load balancing of your services is done manually and it is prone to errors.</li><li>There is an overhead maintaining a “cluster” of applications: Network routing, service discovery, error recovery…</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/280/1*Jm-TMIDfLnlSdEO5QyANvg.png" /></figure><p>Google has solved this problems (and many more) with an amazing product: <strong>Kubernetes</strong>. They haven’t only solved the technical challenges on clustering applications but they have also provided a common language to describe infrastructure (Infrastructure as Code) within a cluster.</p><p>Think about it, the main problem when describing a problem is the common language: Mathematicians can rely on the equations, musicians can rely in the sol-fa but… when it boils down to software deployments, there has never been a common language.</p><p>Now with Kubernetes and the YAML (or JSON files) we can rely on a delimited set of building blocks to describe our system.</p><p>But not everything is as beauty as it sounds: Kubernetes has its drawbacks. The first one is that, being a pretty new project, there is virtually no documentation (curated documentation) around it so the already steep learning curve becomes even steeper.</p><p>Through this series (Kubernetes from A to Z) I am going to guide you through the setup and management of a cluster in Google Cloud Platform as well as the management of a small microservices system.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/286/1*WlUBOiDy6eMISgmwnBzBKw.png" /></figure><p>My idea is give an introduction which will be deep enough to let you start a full project being able to assess if Kubernetes is a good fit for it.</p><p>My idea is to write around one post a week and build, from the very basics up to the most complex tasks, a solid knowledge base that is not going to be only useful to me but to everyone who wants to get into the amazing world of container clusters.</p><p>Please feel free to send me private messages but be aware that I am a pretty busy guy son it might take few days for me to come back to you.</p><p>If you want to know more about microservices, I will also encourage you to read my book which settles the basics that you need to know around microservices:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/1*OZWNwbwF1KHEBm26ncptug.png" /></figure><p>Let the show begin.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ad425051cf59" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>