This is part of Solutions Review’s Premium Content Series, a collection of columns written by industry experts in maturing software categories. In this submission, EasyMorph Founder Dmitry Gudkov comments on the BI stagnation and the current market situation for data analysis tools.
Containers and Kubernetes are designed to take advantage of the power of elastic cloud computing. Much of the early focus at Kubernetes was on stateless computing, with storage relegated to second place. Persistence is the default status in legacy workloads, but is the add-on status in Kubernetes. By default, Kubernetes storage is not persistent. Any storage that is defined as part of a container in Kubernetes is held in temporary storage space that exists as long as the Kubernetes pod exists. Then it is removed.
Older application developers only treat garbage collection as an afterthought. In Kubernetes, storage seems to be a minor matter and data is one container instance away from being permanently lost. There are several of these issues or gaps in Kubernetes backup, disaster recovery (DR), security, and more. Today, solutions that can help fill these gaps are on the rise.
Application Snapshot Management is an important offering on the rise for all Kubernetes developers, regardless of where their workloads are, on-premise or in the cloud. Snapshots give Kubernetes developers the ability to copy a storage volume at a specific point in time without creating a completely new volume. Snapshots also enable database administrators to create backup copies that can be used for recovery or testing.
Snapshot management fills a void where users previously had access to snapshots, similar to a gym membership, but rarely used them. Solutions such as a storage-independent in-place snapshot management solution save companies time and money while strengthening their disaster recovery capabilities. Snapshot management ensures that the gym membership mentality doesn’t get in the way of keeping a relevant and up-to-date copy of data.
Another problem is that traditional storage snapshot management was almost non-existent until recently. SMI-S standards did not hold up and were largely viewed as sub-par retrofits; each storage behaved differently with ROW snapshots and COW snapshots. In Kubernetes, snapshot standardization was approached very early with the Container Storage Interface (CSI) initiative. There are already over 50 storage providers who adhere to it.
Another way to improve the Kubernetes ecosystem is to improve cyber resilience. Cyber ââresilience is the ability of an organization to prepare, respond to, and recover from a cyber threat. Cyber ââresilience means that when a company is threatened, it is not without power. It can detect, adapt and effectively respond to cyber threats. Cyber ââresilience is an important part of the backup and disaster recovery strategy (BUDR) today.
DR has taken a back seat with the fault tolerant architectures of Elastic Cloud Computing, so it is important to consider solutions that protect users from cyberattacks with tamper-proof backups. User-friendly Kubernetes backup services are now available to protect multi-cloud, multi-cluster, application and cloud-native databases, bridging the data management and protection gap between DevOps and IT operations.
With cyber attacks growing exponentially, companies invest a lot of time and energy in ensuring good insurance. That, combined with the real “on-site” facts of new users who are not used to managing backups, is the new defensive front line. They understand backups, but they are often not battle-tested and some of the best-practice rules are often not the most important thing to them. This is where a backup service comes into play, which takes care of the maintenance of a separate backup infrastructure and helps IT teams to subscribe to the company’s data protection guidelines in a simple and understandable way.
With the ongoing adoption of Kubernetes, it’s good to keep in mind that it allows more input than a more mature ecosystem and therefore requires flexibility and a versatile architecture. As the ransomware threats to Kubernetes increase, it is important to consider DR and backup strategies beforehand to combat the ever-changing threat landscape. For solution developers and innovators, this is an exciting notion and an opportunity to move to the left to make real changes in the development cycle.