In the past few years, traditional relatives have been busy scoring databases and data models. But why, actually? Do they not have enough power? If you look at existing trends, each one says, “Use the same separate table, leave the relationship.“Flat tables can appeal because they are easy to read and fast to inquire. The responsibility of the command inquiry (CQRS) is also developed on the same idea: There are additional data copies for the Trade of Quick Reading. For the first time in 2013, I tried the CQRS. It felt like a superpower. But the price was. Maintaining all these event handlers and separate writing models requires time and energy.
Of course, CQRS is not the only model that removes us from a relative data model. People say, “Store data in terms of use.” Sometimes this is a table in the SQL, or maybe only one file in Mango DB, or S3. This is called polyglytroot perseverance. But why do we jump this direction? Because this trend is? Then, before we feel, we have created the mess of the match. Related databases shine for a reason: consistency and integrity. We should not ignore them. They bring real benefits.
