3 ms·
Both are in the business of storing data that can later be retrieved again, so I don't think your analogy really holds in this case. Maybe you are thinking of o
by jurre 14y ago
Both are in the business of storing data that can later be retrieved again, so I don't think your analogy really holds in this case. Maybe you are thinking of one particular nosql solution but I think almost all projects could find an alternative to a database that uses SQL. That is not to say that it shouldn't be a relational database or that there's a one shoe fits all solution out there.
- GlennS 14y agoI think you would really struggle to find adequate replacements for relational databases in at least two areas: reporting and ad-hoc queries.
- viraptor 14y agoMongodb has ad-hoc queries (not as simple as SQL, but still). Many engines can run huge aggregated queries (hadoop?) But I think the problem is placed in the wrong place. If SQL the language/API is copyrighted, then isn't it easier produce a new API with the same functionality?)