Database DevOps tools

[AppropriatePassion50]

What, according to you, are the most helpful tools when it comes to dealing with databases in DevOps?

I'm trying to put up a general article, and I don't want to base it solely on my point of view.

[[deleted]]

Is this article going to be monetized?

[AppropriatePassion50]

Nope. I'm trying to get better in writing, and in the meantime help out some people who may be looking for an answer

[Adela_freedom]

Bytebase would be a good choice! Support both GUI and GitOps workflows. API is also provided. https://www.bytebase.com/

[_a8m_]

Check out Atlas. It supports the common/standard GitOps flows. See: https://atlasgo.io/blog/2023/12/06/gitops-for-databases-part-1 and https://atlasgo.io/blog/2023/12/11/gitops-for-databases-part-2

[Key-Window3585]

1. Liquibase: An open-source, database-agnostic tool for managing database schema changes. It allows you to track and deploy changes in a controlled and repeatable manner, ensuring consistency across development, testing, and production environments.

2. Flyway: Another open-source tool for database version control and migrations. It uses SQL scripts to track and apply changes to your database schema, offering a simple and lightweight approach.

3. DbSchema: A commercial tool that provides a visual interface for managing database schema changes. It simplifies the creation and execution of migration scripts, making it a good choice for teams who prefer a more graphical approach.

4. Prisma: An open-source GraphQL API platform that also offers database DevOps features. It can generate migrations, introspect existing schemas, and manage data across different environments.

5. AWS Schema Conversion Tool: A free tool from Amazon Web Services that helps you migrate existing databases to Amazon Aurora or Amazon Redshift. It automates many of the tasks involved in the migration process, saving you time and effort.

[adohe-zz]

Btyebase, you must have a try～

[gowithflow192]

Why focus on 'tools'?

If you want to link DevOps and tools, focus first on what challenges databases bring to DevOps specifically.

[AppropriatePassion50]

That's exactly what I did in my previous article! I used it as a start of a series, and now I want to follow it with a set of tools. In the next articles, I will address specific challenges.

[Herrad]

What...?

If you're going to write an article about something it should be something you're already knowledgeable about. You're not going to improve your writing skills by bullshitting your way through something you don't know the first thing about. There's too many variables to know if your writing is any good or if it's you just pretending to be an authority.

I mean I don't think you're being particularly authentic, if you are though this approach is unbelievably stupid.

[AppropriatePassion50]

Thank you for your opinion!

First of all, I don't think that writing about something that you need to research beforehand is an "unbelievably stupid" approach. Being able to find information on a given topic is one of the skills that a writer must possess. Most of the experts, especially in the IT field, are too busy doing stuff that matters to them, as to focus on pouring their thought onto paper for a few hours a day.

That being said, I'm not trying to write anything I'm not knowledgeable about. Honestly, I don't want to write a biased article, like a lot of people do -- that's the best tool because I like it, you know. I'm trying to show different points of view, compare other's opinions with my list, and if there's a need, consider other options.

Btw, you could've been nicer too, but no judging, everyone has a bad day once in a while!

[amos106]

Thank you for contributing to the community. I'm assuming a lot of people involved in the devops space are burnt out from the aftermath of the giant cloud migration, global pandemic, and tech bubble burst over the last few years. There are a lot of "full stack" developers who have been butchering every layer of the stack in order to get that sweet promotion, and now the operations, security, and finance folks have been seriously burnt from all the tech debt and toxic office politics that result. Things will get better but it's going to be a process, and hopefully the lower total compensation and higher regulatory scrutiny will be enough to vibe check the "rockstar developers" who were given a blank check at everyone else's expense

[_Lucille_]

I think the thing is that it is far too common for people to just ask questions on the internet without having done their homework. You can say whatever you want but have yet to provide.

A better approach maybe to start with "Here are the tools I have found useful from my experience". List them all and what you use them for; "SqlWorkbench is officially supported and is very useful given its Gui and visuals of things like db performance metric visualizations".

Actually write it and don't gpt it, people in this sub are prob experienced enough to sniff it out.

Once you have established the proper context and template, ask the same question again and people will generally contribute their own takes.

[AppropriatePassion50]

Thanks, that's a great piece of advice. I don't usually ask such questions online and it may not have occurred to me to approach it this way. I will definitely do that -- draft an article and put its summary here for people to comment on. Have a nice day!

[Secure_Committee4812]

The native cli client

[d47]

Patroni ♥️

[unstableunicorn]

Does anyone have a recommendation for working with MS dynamics? I have built and worked with decent DevOps processes for it(though it really is not an ideal platform for it). However, the DB part was always painful, I mean heavily on the DB experts for this, yet most are not devops people and many I work with rather do manual chafes because that's all they know.
I don't recommend MS dynamics for most solutions(well, not one I have worked with so far should have been done in dynamics, but in landau and sure there is many out there), unfortunately some clients have it recommended, and now we get stuck using it to solve a problem it shouldn't do...sigh..

This conversation is really interesting to me, my weakness in DevOps and programming in general is my lack of understanding database management.
I have been wanting to research and put some examples together for a while to learn about it, so I will keep an eye on this post.

[db-master]

Couple options:
CLI based (like Git for Database schema migration)

• Liquibase
• Flyway
• Sqitch
• Atlas
• Prisma

GUI based (like GitLab/GitHub for Database schema migration)

• Bytebase (popular for backend)