3 ms·
I dunno. It might depend on which NoSQL folks we are talking about. Certainly the array-native database folks are not even close to the relational use case.
by einhverfr 14y ago
I dunno. It might depend on which NoSQL folks we are talking about. Certainly the array-native database folks are not even close to the relational use case.
I also think the best way to look at NoSQL is that it is just a further development on Stonebreaker's bottom-left quadrant database division--- object databases.
The more I get into it, the more I am astounded with the power of PostgreSQL to take over all these workloads on the low-end and more.
- its_so_on 14y ago"The more I get into it, the more I am astounded with the power of PostgreSQL to take over all these workloads on the low-end and more." Exactly. When NoSQL "honestly" say, oh nooooooooo we're not replacing the traditional RDBMS approach, this is anything but honest. It's like me building this suspended-rail system for inner-city transportation. Oh noooooooo I'm not replacing traditional cars and bicycles! the way you get acceptance is by faking honesty that you're not at all replacing the traditional approach (that you're replacing.)
- einhverfr 14y agoBut in this case at least you are using PostgreSQL outside of anything even remotely purely relational. It is at least object-relational, and often key-value-id (like hstore) or document store (JSON or XML). The power of PostgreSQL occurs from the power to ignore the relational model and take other approaches when it is helpful.
- its_so_on 14y agoto be honest I lost track of the thread. I don't know what we're talking about anymore.