Should be titled, "consider the cost of compliance tooling when picking a DB". Strange article, I'm not sure what the point is.
Lunch isn't everything. Even though many people eat lunch, lunch isn't the only thing you should consider when eating. For instance, there is also dinner, and dinner has a different set of characteristics than lunch. When deciding what to eat today, remember to consider both lunch and dinner. There may be other considerations as well, such as breakfast, that are not discussed here.
I personally like Pat Helland's paper, "Life Beyond Distributed Transactions: An apostate’s opinion", which goes into "practical approaches used in the implementations of large-scale mission-critical applications in a
world which rejects distributed transactions."
Indeed. You don't need a documentdb. Your schema-less store actually contains a whole set of objects that have the same schema.
And you'll want to normalize that data. So do that.
Graphs? Please, spend 2 weeks looking at why you feel a behemoth like Neo4j is actually necessary in your system. Because it probably isn't. Please don't confuse ease of navigation with the need for a graph database.
yeah, that was really brief. I was actually hoping for someone to bring up https://arxiv.org/abs/1901.01930 (keeping CALM) for an interesting alternative
Lunch isn't everything. Even though many people eat lunch, lunch isn't the only thing you should consider when eating. For instance, there is also dinner, and dinner has a different set of characteristics than lunch. When deciding what to eat today, remember to consider both lunch and dinner. There may be other considerations as well, such as breakfast, that are not discussed here.