> without having to worry about specifying a schema upfront that may change over time. Thing is, there's always a schema. Code always expects data to look a pa

> without having to worry about specifying a schema upfront that may change over time. Thing is, there's always a schema. Code always expects data to look a particular way. Whether it's written down and enforced by the DB or not will have a great influence on your ability to reason about your system and make changes down the line. This sounds like the same mistakes of Mongo all over again. Databases that don't require and enforce schemas trade a degree of early flexibility and development speed for a future of confusion, hacks and workarounds, and lower velocity. Most people who make this tradeoff aren't aware they're making it. The rest of us use RDBMS. (I get that you work for the company and I don't expect this comment to change anything - except hopefully the mind of someone contemplating using a no-schema database)