MySQL and Backups as a Service
MySQL and Backups as a Service
Learn about the recent announcement that MySQL is now going to be available as a Platform as a Service (PaaS) offering through Azure and what it means for you.
Join the DZone community and get the full member experience.
Join For FreeCompliant Database DevOps and the role of DevSecOps DevOps is becoming the new normal in application development, and DevSecOps is now entering the picture. By balancing the desire to release code faster with the need for the same code to be secure, it addresses increasing demands for data privacy. But what about the database? How can databases be included in both DevOps and DevSecOps? What additional measures should be considered to achieve truly compliant database DevOps? This whitepaper provides a valuable insight. Get the whitepaper
With the recent announcement that MySQL is available as a Platform as a Service (PaaS) offering through Azure, a lot more exciting opportunities have presented themselves for companies to build and manage their information. According to the DB-Engines Ranking, MySQL is the second most popular data management system out there. At last, you get to incorporate it directly into your Azure ecosystem. While there are tons of reasons this is exciting, I’m going to focus on one very particular issue, backups.
Why Are Backups Important?
I’m not going to answer that question. Everyone knows that backups are important. Everyone knows that they need to have backups. Yet… There is example after example where people either haven’t bothered to set up backups or didn’t know what a real backup entails, or even had backups, but never did any validation. I gathered a few examples of failed backups that literally destroyed companies in this article. Funny enough, a couple of them were running on MySQL. A backup is vital to the business. Even more important, a validated backup is vital to the business.
Why Is MySQL Platform as a Service Important?
I am going to answer this question. There are a lot of advantages to creating, using and developing against data storage within a PaaS offering. One of the biggest for me is backups. Microsoft is automatically taking backups of the MySQL databases you create within Azure. These are real, full backups. Microsoft validates the backups. As I write this, you’ll have the ability to restore your entire database, to any point in time, at intervals of five minutes, over a 35-day preceding period. By programming against a MySQL database within Azure, you are gaining the protection of the information you’re storing within your database, and you don’t have to do anything to benefit from this. It’s all part of the service.
MySQL Protection
Finally, with Microsoft’s release of MySQL within Azure, you not only get a well-performing and maintained MySQL database, you get backups. Consequently, protection of your data, built into the service, at no added cost, is a vital part of what Microsoft delivers for us through MySQL on Azure.
Watch this space. As soon as I get the chance to more thoroughly test the self-service restore option I’ll create another blog post detailing how it works. In case you didn’t notice, they’re hosting PostgreSQL as well, and it has backups in place.
Compliant Database DevOps and the role of DevSecOps DevOps is becoming the new normal in application development, and DevSecOps is now entering the picture. By balancing the desire to release code faster with the need for the same code to be secure, it addresses increasing demands for data privacy. But what about the database? How can databases be included in both DevOps and DevSecOps? What additional measures should be considered to achieve truly compliant database DevOps? This whitepaper provides a valuable insight. Get the whitepaper
Like This Article? Read More From DZone
Published at DZone with permission of Grant Fritchey , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}