Move off SQL and let's do overview the world of no relational data
Regularly in courses, interviews, candidate requirements, and job descriptions for analysts, you'll find mentions of proficiency in relational models. However, there is more than one data organization model in database systems: key-value, object-oriented, graph, document-oriented, and various others. Moreover, there are different frameworks that completely separate the application layer from how data is organized in the model.
Let's share a couple of thoughts from architects on how an analyst should navigate such a situation and what they should do with data models to make it less painful later on.