I hate video links. The information could have been a few paragraphs of text that I could glance. Instead this much minutes of video that you can't search, glance over, read while listening to something else… So it's a pass for me.

First, persistency. You data lifecycle may not be directly proportional to your applications lifecycle. You may need it even after the app is shut down.

Second, RDBM systems provide a well defined memory/storage structure and API - "structured query language". This enables you to easily query your data and acquire suitable views that are beneficial for your applications purposes.

Third, It's always better to outsource your data layer to a battle tested, and trustworty database then trying to reinvent the wheel.

So this paves a road for you to focus on your business logic than splitting that focus for the data layer and business logic.

I suppose it's "confusing perspective" worthy.

Then I hope it won't get any traction.

I hope this is a joke and not intended to be real.

What? The? Fuck?

Python docs are mostly “reference” material. Which means it’s not intended to show you how things are done, but used as detailed descriptions of commands/statements/classes/methods.

This is why you are having trouble understanding it. You first need to go understand fundamentals of it and they will be useful when you need details and intricacies of something while using it.

I want to see the 10x hamsters!

It’s not the real issue. I introduced that while anonymizing the data. It’s that a 3-5 liner code became a huge switch case by just incrementing the code and never thinking how it should be done. This was caused by like 15 engineers in time :)

Something like below would be huge improvement:

subs1 = ["cluster1", "cluster2"]
if subs1.contains(clusterName) return subs1