1. 5

    This is very short-sighted in my opinion. Using raw kubernetes when you’re a small company/startup can be a huge mistake, as there will be a lot of low-level ops work to do in order to operate the cluster. The same goes with using microservices in the early days of a startup.

    Finally, I’m still waiting to see actual data on “containers are less expensive”. I’d expect a monolith running on a single, or couple of instances to be way less expensive than a full cluster with 20 services on it.

    1. 2

      Hi Damien, I’m Dan — the author of the blog post. The article is not meant to suggest that Kubernetes is a solution to every problem. And It doesn’t aim at starting a debate whatever microservices or monoliths are the right (or wrong) way to build applications. I apologise if it came across that way. The article is meant to explain the reason why Kubernetes came to be in the very first place. Most of the “What is Kubernetes?” articles on the internet do a very poor job of explaining why we need such a complex system. And they don’t set the scene on why it was created in the very first place. If there’s something I could do to make it more clear, please let me know and I will amend the article. Thanks for taking the time to share the feedback.

      1. 2

        Containers are a lot lighter than virtual machines so if you are running a lot of VMs you could save money switching to containers.

      1. 3

        Hi, I’m Damien. I occasionally write at https://dmathieu.com

        1. 6

          I am building a wireless speaker using a raspberry, their speaker bonnet and raspotify. The idea is to build one in each of our main rooms (living room, bedroom, office), and hide them inside cute vintage objects.

          1. 3

            I’m finishing Writing an Interpreter in Go. Not as technical as it sounds, and definitely awesome.

            1. 2

              Is this a decent primer for learning go coming from a C# background?

              1. 1

                sorry for the (way too) late reply. I wouldn’t use this book to use Go. Though the language is used, it’s very basically done so.

            1. 2

              I have 2 phones.

              A Samsung Galaxy S8, paid for by my employer that I carry when I am on-call. GMail/Inbox aren’t installed there. So I don’t have access to work emails. I use it for calendar notifications though. Only pagerduty knows the phone’s number.

              My personal phone is the new Nokia 3310, which only can send texts and make phone calls (I don’t even have a data plan. So no MMS).

              When I’m on-call, I’ll be carrying both phones (usually one in my pocket, the other in my backpack). When I’m not on-call, I’ll only have my personal phone.

              1. 2

                Nice work! What are you using to build new docker images (I suppose your own computer isn’t ARM)?

                1. 1

                  I don’t like the single points of failure, but other than that it looks cool.

                  1. 1

                    It’s not meant as a highly-reliable cluster :-)

                    1. 1

                      Isn’t that the purpose of a cluster though?

                      1. 1

                        Of a production one, yes for sure. As I mentioned, the goal isn’t to build a production cluster, but to learn.

                        Also, removing all SPoF here would mean 2 masters, and 2 load balancers, with load balancing on both. On raspberry pis at home, this could get very messy quite easily.

                  1. 1

                    Two laptops, one for work, the other for personal stuff. I don’t have personal email/facebook on the work laptop; I don’t have any work stuff on the personal laptop.