3 ms·
As someone who participated in building the first wave of NoSQL, I have to agree with the sentiment here. Except tabular inflexibility hits everyone. I wrote a
by jchanimal 8y ago
As someone who participated in building the first wave of NoSQL, I have to agree with the sentiment here. Except tabular inflexibility hits everyone.
I wrote a blog post about how FaunaDB offers the best of relational and NoSQL models here: https://blog.fauna.com/unifying-relational-document-graph-and-temporal-data-models https://blog.fauna.com/unifying-relational-document-graph-an...
- mamcx 8y agoAs hobby I'm building a relational language, and think the problem that the RDBMS folks have overlooked is how operate in partail relations (like slices or tables with less + more fields). You are set with the initial schema and that is. Is not easy to store arbitrary portions of relations, not is even easy to operate in-memory instead. Plus, the fact the DB is far from the code miss a lot of oportunities. In my mind, I think the solution is not to have a "database language + storage far away" but code all the app with a embebed db. Is not as weird as it sound. This is how we operate with foxpro.