<story><title>Kubernetes for personal projects? No thanks</title><url>https://carlosrdrz.es/kubernetes-for-small-projects/</url></story><parent_chain><item><author>jypepin</author><text>I totally agree with this article. I&amp;#x27;m giving a point of a view of a pure developer who knows nothing about DevOps things and managing servers.
I kind of know what NGINX is and barely know how to configure something like systemd.&lt;p&gt;I recently setup a digital ocean droplet and setup my blog there to actually understand how it works. It was great because I learned a ton and feel in control.  
Pretty simple setup - single droplet, rails with postgres, capistrano to automate deploys and a very simply NGINX config.  
It took me multiple days to setup everything, compared to the 5 minutes Heroku would have required - and it&amp;#x27;s not as nice as what Heroku offers.&lt;p&gt;Still, I&amp;#x27;d wait as long as I can to get out of something so simple as Heroku for _anything_.  
I understand it gets expensive quickly, but I really want to see the cost difference of Heroku vs the time spent for the engineering team to manage all the complexities of devops, automated deploys, scaling, and I&amp;#x27;m not even mentioning all the data&amp;#x2F;logging&amp;#x2F;monitoring things that Heroku allows to add with 1 click.</text></item></parent_chain><comment><author>Draiken</author><text>&amp;gt;  I understand it gets expensive quickly, but I really want to see the cost difference of Heroku vs the time spent for the engineering team to manage all the complexities of devops, automated deploys, scaling, and I&amp;#x27;m not even mentioning all the data&amp;#x2F;logging&amp;#x2F;monitoring things that Heroku allows to add with 1 click.&lt;p&gt;Well, if you use a k8s cluster on GKE for example, you will have literally all those things by default. Not even a click needed.&lt;p&gt;IMO running your own Kubernetes cluster for a company is insanity unless you have a very good reason to do so.</text></comment>
<story><title>Kubernetes for personal projects? No thanks</title><url>https://carlosrdrz.es/kubernetes-for-small-projects/</url></story><parent_chain><item><author>jypepin</author><text>I totally agree with this article. I&amp;#x27;m giving a point of a view of a pure developer who knows nothing about DevOps things and managing servers.
I kind of know what NGINX is and barely know how to configure something like systemd.&lt;p&gt;I recently setup a digital ocean droplet and setup my blog there to actually understand how it works. It was great because I learned a ton and feel in control.  
Pretty simple setup - single droplet, rails with postgres, capistrano to automate deploys and a very simply NGINX config.  
It took me multiple days to setup everything, compared to the 5 minutes Heroku would have required - and it&amp;#x27;s not as nice as what Heroku offers.&lt;p&gt;Still, I&amp;#x27;d wait as long as I can to get out of something so simple as Heroku for _anything_.  
I understand it gets expensive quickly, but I really want to see the cost difference of Heroku vs the time spent for the engineering team to manage all the complexities of devops, automated deploys, scaling, and I&amp;#x27;m not even mentioning all the data&amp;#x2F;logging&amp;#x2F;monitoring things that Heroku allows to add with 1 click.</text></item></parent_chain><comment><author>de_watcher</author><text>&amp;gt; giving a point of a view of a pure developer&lt;p&gt;Kubernetes really looks like designed by the software developers for the software developers: dump all configs of your services in one place, imagine that they run on the network. The uninteresting parts of the job (like managing nodes and ingress, fixing internal overlay network and DNS, adding services for centralized logging) aren&amp;#x27;t mixed with the actual services. Obviously, the package management is solved by using containers (essentially OS images) as the package format.</text></comment>