There's a little too many of his examples I've seen in the real world. We where trying to bid on hosting an application that required Cassandra and Kubernetes.

There's a little too many of his examples I've seen in the real world. We where trying to bid on hosting an application that required Cassandra and Kubernetes. The application was built that way, that was how it currently ran. The customer wanted to move to Azure and try to save a bit on hosting. We reached the conclusion that they could use CosmosDB with the Cassandra API enabled and given that it was just a single container it could actually just run in Azure Websites, no need to Kubernetes. Then we started to dig into what the application did, and how much traffic it received. It was just a few hundred http requests per day, and a stable 2GB of data. This should just have been a tiny Java application and SQLite or MariaDB. We did not win the bid, neither the customer nor the developers seemed please with our conclusions. Kafka is another fan favorite with developers. It's not that Kafka isn't great, it is, but if you are only pushing a 2500 messages per day, it's a bit heavy on infrastructure, maybe just stuff those messages in your database. We've build infrastructure for large national projects (in a small country) and you can easily service an entire population on a single MariaDB on a modern server and few VM for the application.