DevOpsing Your Database
Working on database-backed, internet-based systems for over a decade, Robert is a long time user, developer, and advocate for open source technologies. Best known for his work in the Postgres community, he has contributed to numerous industry groups and is currently a co-organizer for both Baltimore and DC DevOpsDays conferences. An international speaker on databases, open source, and web operations, he occasionally blogs at https://xzilla.net
No video of the event yet, sorry!
Most of the focus for DevOps has been focused on cross-pollinating development practices and operational concerns throughout the deployment pipeline, but a lot of the conversation leaves out what is often the most critical part of your technology stack: the database. Perhaps that’s because DBA’s have always had to keep one foot in development and one in production, before there was a devops. Or maybe DBA’s just suck at playing well with others. Bottom line; it doesn’t matter. If you are going to store data, you need a plan that both developers and operations people can understand and embrace.
Just as there are many different ways to "Do the DevOps", there is no one answer, you need to understand your companies needs and then make the appropriate trade-offs. That said, nearly a decade into the devops movement, we’ve found there are commonalities across high functioning devops organizations. It’s not so much about the tools, but about the techniques they use to help people break down barriers between different roles and establish a common ownership of technology within their organizations.
Monitoring and visibility, managing schema changes and production pushes, optimization, configuration, and backups; there are aspects to data storage that bring about unique challenges. You won’t need to adopt all of these techniques to be successful, but it’s time you had a frank conversation about what it takes to make your database truly “webscale”.
- 50 min
- PostgresConf US 2018
- Operations and Administration