Have you included your databases in your DevOps pipeline? Databases are frequently not included when transforming an application and engineering culture towards a DevOps or continuous deployment engineering organization. And, you could be forgiven for this, because setting up repeatable, fast, and up-to-date database environments for an application is really hard!

Join me for a live demo and technical best practices for setting up your databases in your DevOps workflow. I will show you how to:

➡️ Set up continuous database deployments
➡️ Run a sample CD workflow for test and back up your database on push

*Flow:*

* Introductions
* Technical best practices for database DevOps
* Intro to GitHub & GitHub Actions Demo
* A high-level overview of the project
* Go through the demo
* Q&A

*DevOps for Databases Technical Best Practices:*

* To begin with, databases were never part of the original DevOps vision.
* Lack of culture and well-established processes
* Microservices are a good way to decouple the database.
* The database schema, including indexes, need to be in source control.
* Data that controls business logic such as lookup tables also need to be in source control.
* Developers need a way to easily create local databases.
* The shared database should only be updated via a build server.
* Migrations to the rescue
* Practice in a production-like environment
* Monitoring database systems for performance and compliance, taking into account regional differences and regulatory requirements.
test!
* You need to test a change before applying it to a production environment.
* Containers are a good way to practice.

My code: [https://github.com/singlestore-labs/singlestore-and-github-actions-demo](https://github.com/singlestore-labs/singlestore-and-github-actions-demo)

You can view a complete list of my past and upcoming talks with video on my website [https://www.joekarlsson.com/speaking](https://www.joekarlsson.com/speaking/).