Kubernetes? Database Schema? Schema Management with Atlas Operator

This video explores the fundamentals to master database schema management using Atlas Kubernetes Operator. Learn how to efficiently manage your database schemas in a Kubernetes environment, improving scalability and reducing maintenance efforts.

#database #kubernetes #databaseschema

▬▬▬▬▬▬ 🔗 Additional Info 🔗 ▬▬▬▬▬▬

▬▬▬▬▬▬ 💰 Sponsoships 💰 ▬▬▬▬▬▬

▬▬▬▬▬▬ 👋 Contact me 👋 ▬▬▬▬▬▬

▬▬▬▬▬▬ 🚀 Other Channels 🚀 ▬▬▬▬▬▬

▬▬▬▬▬▬ ⏱ Timecodes ⏱ ▬▬▬▬▬▬
00:00 Introduction to database schemas in Kubernetes
04:08 Atlas Kubernetes Operator in Action
17:50 Atlas Kubernetes Operator Pros and Cons

[DevOpsToolkit]

Which tool do you use to manage database schemas?

[RafaelDurelli]

These new video introduction are really nice lol 🎉🎉 I always watch with my daughter too

[JordanCricketMoore]

Naming things is hard. Not to be confused with MongoDB Altas Operator

[shibak]

This seems to be a tool created by people who know databases exist but they've never been a part of a data team or don't understand how complex a database and its design can be. A solution developped by a newbie who has learned one language or tool and now thinks that EVERY problem has to be solved with the same language/tool. It's completely fair to look at a database, its resources (such as storage), its networking and to a certain extent its secrets from K8s perspective. After all, k8s is effectively an abstraction of OS and all those things are justified paradigms within the context of K8s. In fact you yourself had explained how many used to think that DBs don't belong to k8s because they didn't know how to use k8s the correct way. But defining a (e.g.) db table as a k8s resource is just an admission that one is obsessed with k8s and possibly doesn't know any tool other than that (or doesn't know about database design and data modeling enough). I'm sure many SRE folks used to think of Terraform as the right environment for expressing data elements, too. But that's as wrong as defining a table as a k8s resource! DB practitioners have had a portfolio of tools for schema management: Liquibase, Flyway, Alembic, Sqitch, DBMaestro, or modern tools like SqlDBM are built for that purpose and fit well within the workflow of DBAs, DB developers or analytic engineers. Managing a k8s resource has nothing to do with the day to day workflow of any of those three. AND all those tools have spent a huge amount of time adapting to the needs of DB developers: DBs are not made of just a handful of tables in one schema! You have to think about security design (i.e. multiple schemas, multiple users, privileges of the users, creator rights vs user rights, etc) and all sorts of different DB objects such as constraints, indexes, functions, stored procedures, triggers, views, materialised views, schedules (yes, many DBs have internal task schedulers), etc. Do you think a DB developer would be productive swimming in a sea of YAML definition to get to a db object definition in SQL?! This tool will only serve folks who are obsessed with K8s. No real development team which is building/maintaining/running a serious application would adopt this for maintain their data model.

[jonny.rubber]

At the moment we are using EF core to migrate databases for our own apps. After deploy, we call an API endpoint.

[SranSrepfler]

Need to watch it in full but many companies will stick to Liquibase and Flyway until there's a direct k8s support via an operator. I noticed LB and FW icons on Atlas, maybe they'll expand the operator so they reference those tools resources and apply the changes using the native tools devs have been using so far.

[shwanbekas]

could you please talk about DevSecOps. Thank You

[cowgod]

Looks like a very nice solution. Does Atlas support data migrations as well? Sometimes my schema changes also require some UPDATE queries to adjust the data to match the new schema.

[mopsikever]

Great video but the fact that you need to manage multiple schemas inside the same CRD will eventually fail since every object in k8s has a size limit due to etcd limitations. Hopefully they will implement a queue for each CRD.

[skies]

wait. you guy use operators for this? helm hooks is what we use

[aguafria]

Lol what schema management. Literally all I did was run a job with an init script.

[typicalaimster]

I was excited thinking this was for Mongo Atlas. Only to be disappointed.