Menu
Say you're coding some kind of web application. Something where people can contribute content, e.g. a simple photo-sharing site.
How many good reasons can you think of to not go with an object-oriented database (e.g. db4o)?
440
Object databases are commonly used in applications that require high performance, calculations, and faster results. Some of the common applications that use object databases are real-time systems, architectural & engineering for 3D modeling, telecommunications, and scientific products, molecular science, and astronomy.
Although Object Oriented Databases failed because they could not address the need for easy access to the raw data, we soldiered on with OO languages and thinking tools, all the while translating back and forth into data at every interface. The advent of micro-services, unfortunately made this problem worse.
Object-oriented databases provide a number of advantages over relational databases like ease of extensibility, custom data models, provision for modelling complex data structures and faster access time. But they do lack in certain areas and have no strict standards and implementation mostly depends upon the vendor.
One disadvantage of OODBs is poor adoption among the community. Although the model has been established since the 1980s, up to now, very few database management systems have taken to object databases. The community that works with the model is correspondingly small.
An OODBMS is better if you only need to access your data through your objects. If your solution requires additional pathways to your data (e.g. ad-hoc queries, reporting, other applications that need data access but can't make use of your objects), then a traditional RDBMS system is better.
Note: OODBMSes have made a lot of improvement in this area.
189
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
