1. 7

  2. 2

    Sometimes I suspect that Kubernetes, along with the whole orchestration paradigm, is one of Google’s ways to make sure no competitor ever gets off the ground.

    1. 2

      But with an ambition to build the best current account in the world and scale it to hundreds of millions of customers, we knew that we had to be the bank with the best technology. Daily batch processes, single points of failure, and maintenance windows are not acceptable in a world where customers expect 24x7, always-on access to their money, and where we want to roll out new features in a matter of hours, not months.

      A large scale failure in a distributed system can be very difficult to understand, and well-intentioned human action can sometimes compound issues, as happened here.

      And this is why you don’t have three times as many microservices as you do engineers.