2 ms·
Major schema changes can also be done in a backwards compatible/recoverable way - I like to follow this procedure. Specifically the "The Five Phases of a Live S
by sojournerc 6y ago
Major schema changes can also be done in a backwards compatible/recoverable way - I like to follow this procedure. Specifically the "The Five Phases of a Live Schema Change" section: https://queue.acm.org/detail.cfm?id=3300018 https://queue.acm.org/detail.cfm?id=3300018
- bob1029 6y agoWe have spent a lot of time to make our schema as stable as possible in the face of potential changes. In places where we might end up with 100+ columns that vary wildly depending on context of use, we use JSON documents which can store objects of arbitrary complexity. This is a very delicate balancing act for us, because we also like to be able to write SQL queries against important business keys, and having those wrapped up in JSON can make it difficult to get good, fast results. In many cases we will duplicate the storage of some information so that it can be indexed as well as be available in the complex object graph.