Geek Answers Handbook

When should I use the object database?

I have been using relational databases for some time and have recently come across another database: an object database. One of the products built around this idea had a description: a scalable "post-relational" database with a multidimensional data and application server for distributed web applications.

This makes me wonder when should I use such a database? I mean, Facebook should use MySQL, and everything seems to be in order, and this can be seen as a large-scale distributed web application. The same goes for some other web applications such as Twitter and Orkut. Given that this is so, when should I use the Object database?

+5
source share
1 answer

Feature databases work really well when you have deep feature graphs (like CAD or finite element models with lots of geometric features). Running all of these JOINs in a relational database would be prohibitively expensive, but natural for an object database.

+3
source

More articles:


All Articles