I have spent most of my career dealing with data structures and schemes. Traditional relative databases are terrific to handle well -defined columns and fixed tables, but need to change the needs of the moment or add new fields, I have seen that teams update schemes day or weeks, writing migration and releasing. When running multi -tenant applications, it becomes even more complicated, where different tenants can have different sets of different features for the same type of existence.
I would like to explain how I handle these challenges and take advantage of the JSONB column type of Postgravis QL, together with the dynamic Rest API design (using fast and points and deper) in the .net Core. This approach has helped me to develop and inquire specific attributes related to the data structure or tenants without re -writing the entire parts of the database scheme. Below, I will run through JSONB offers, why I feel so helpful, and how do I create closing points that allow users to filter and recover data in flexible ways.
What is Jsonb?
JSONB Post Grace QL has a special data type that stores JSON …
