When starting a new project or adding significant functionality to an existing one, you’ll likely face an important question: “Which database should I use?” With hundreds of database systems available—such as MySQL, Cassandra, Redis, Memcached, and PostgreSQL—choosing the right one can be overwhelming.

To make an informed decision, it’s essential to understand how databases work and why they are designed the way they are. This is where the CAP theorem comes in. It provides a foundational framework for understanding the trade-offs between consistency, availability, and partition tolerance—key factors that influence how databases handle data in distributed systems.

One of the most useful features of Helm is the ability to store state, which allows you not only to expand charts, but also to carefully delete them, clearing away all traces of their presence… However, it’s a good idea to understand exactly how Helm stores the state, which is what we will do in this article.

Introduction

I was just interested in learning how Helm stores state. Understanding this issue is not difficult and everything is cleared in the documentation. As of Helm 3, state is kept secret by default.