Congrats on the launch though!
I worry that object databases were the last attempt to solve the impedance mismatch...
The whole point of that "impedance" in the relational model is to for people to think about their data and describe it in a program-independent way: years of experience in the field is what led to its development and what contributes to its continued relevance. Saying that's a problem with the relational model is like saying that design patterns are flawed because they describe commonly used OO designs.
> To me, it's about reducing the impedance mismatch between your data model and the implementation of that model in the database schema.
I'm not sure what sort of impedance mismatch could exist between a program and a relational model but not between a program and a document model. The latter is trivially implementable in terms of the former.
The whole point of that "impedance" in the relational model is to for people to think about their data and describe it in a program-independent way ....
The relational model is hardly the only way to reason about data in a program-independent way.
... years of experience in the field is what led to its development and what contributes to its continued relevance.
I agree, never said otherwise.
Saying that's a problem with the relational model is like saying that design patterns are flawed because they describe commonly used OO designs.
I didn't say there's a problem with the relational model.
I'm not sure what sort of impedance mismatch could exist between a program and a relational model ...
I never said the word "program," you did. I said "data model." You're conflating the data model with the program code (or maybe you think I am, can't really tell). They are not the same thing.
http://en.wikipedia.org/wiki/Abstract_data_type
All I said is that there are some domains for which relational models make sense and there are others for which document-oriented (or other "NoSQL") models make sense.
I've seen so many market changes in my career and, yet, I still write code in a text editor with a terminal window on its side. All of them under a nice windowing environment.
More seriously, we'll see what we can do meet that list with our tech!
Of course, 300ms is also way too long. Do you mean under stress-testing, with request queuing? 300ms is a mind-boggling quantity of CPU cycles...
We're building a general purpose method of running Ruby applications, so 300 ms is certainly a possible request time (including database, processing things, and rendering a view) for some applications that we may be running.
One of the things we're working on with FathomDB is ways to identify slow queries and help figure out what to do about them. If you're game, you can contact me with the queries and the table structure you were using in SQL and I'll try to figure out what's going on!
So I do seriously want to know what's left... We're always on the lookout for the next feature to add ;-)