KubeFm podcast talks about everything in the world of Kubernetes, learns (controversial) opinions from the experts and explores the successes (and failures) of running Kubernetes at scale.

Should every project start with Kubernetes? And if not, when is the right time to switch without incurring (unbearable) technical debt?

In a new episode of KubeFM, we talk about how the team at Loovatech designed an app from scratch and decided to use Docker Compose to host their infrastructure cheaply and effectively in a single virtual machine.

As the project grew, our team had to make the difficult choice to rearchitect their infrastructure and plan for scalability and fault tolerance.

Main points

Engineers should be more open to trying new things and devoting time to exploring bleeding-edge technology that moves them forward. Additionally, reaching out to the community could help engineers learn more and stay up-to-date with new developments.

The team should maintain a trial and error approach, keeping a learning mindset, and understanding the logic behind different tools and technologies. 

It is important to keep things simple in the early stages and increase the complexity of the product as it evolves.

Using cloud services requires less engineering time, is easier to maintain, and is more cost-effective.

Transparency in customer relations is very important, so Loovatech ensures clear communication with its customers throughout the process.