Object Oriented Database
An object oriented database or an object database management
system (ODBMS) stores objects rather than data such as ingriedents, strings of
real numbers. These objects are used in various languages such as C++ and Java. They can contain attributes which is data
that defines characteristics of an object and there are methods which define the
behavior of an object. These systems
support the modelling and creation of the data as an object. The idea is that
the object orientated database concepts can be superimposed on relational
databases which are more commonly used.
Object Databases are a good choice for use in businesses
that are high performing on complex data. This database is also used for less
complex data because it allows for a smaller team and faster development
because there is only one data model. This database offers many advantages such as
reduced maintenance, code reusability, real world modeling and improved
reliability and flexibility. Real world modeling here has a more complete
fashion where objects are organized into classes of objects and objects are
associated with behaviors, its focus is on objects and not processing.
After to reading through the material that lead me to these
above conclusions, my understanding of object oriented databases was still
pretty weak. With the video found
through the following link my understanding is a more solid. Object oriented
databases are better equip for storing complex data in comparison to relational
databases which can store simpler data like employees names and hire dates
where orientated data bases can store media, graphics, CAD and even
geographical satellite information. There is a terrific analogy referring the two
to cars where OODMS is like a car that you drive into a parking garage and turn
off the engine until you are ready to use it but relational data base you would
have to break down the car into parts, put the pieces on different shelves then
put it back together the next time you want to use it which leads to mistakes
and errors. A special language would be
needed to put the relational information together as intended where OODMS would
need no such language only to be told to start. Allowing data to be found where
relational you would have to lock the table to change just one thing. Now I
understand OODMS is capable of holding more complex data but is capable of
being accused quickly and efficiently.
Jianfeng Xiao
I like how you found an article that was able to relate back to how object oriented data bases could be used in creating a design. Having tools that are able to calculate data in an efficient and fast way such as the application you discussed will help designers and engineers make their projects more efficient and more functional.
Chris Thach
I agree that databases have come a long way in the construction world. Working on several projects over co-ops, I have seen how important databases can be even to keep track of small things such as employees, work hours, project hours and so on. This not only helps to keep projects organized and efficient but by being able to reference information in a quick and easy to use database allows for companies to be more liable and have proof and back up if something was to occur or if plans deviated from what was intended.
Carlos Hillinger
Your description of the difference between the two was great, I wish I had read it before performing my own research to get a better foundation of the difference. Some definitions out there are very complex and just understanding objects like photos and videos are what is put into object data bases versus code used for relational databases helps to understand why object orientated databases may be easier to manage.
Luciana,
ReplyDeleteI found the point of superimposing the OODB approach onto relational schema very interesting and would like to see how this is done. I'm sure the original integration may be challenging, but the idea of updating a system with a new type of DBMS is an exciting one considering how much time it would save compared to creating a new one all-together.
Like you, I know nothing about object oriented databases (I honestly barely understand the types of databases as a whole). The analogy you added to your post was very helpful in gaining a better understanding of OODMS and relational databases. It’s interesting that OODMS can handle such complex data but makes it easier to access. I’m still not completely sure I understand OODMS, but your post helped me at least gain a bit of knowledge on the topic.
ReplyDeleteLuciana,
ReplyDeleteI enjoyed reading through your posts. I also researched on OOD and there are many things that are easy to miss when researching, which I learned by reading your post. For example, I did not realize that Object Oriented databases require much less maintenance, and that their code is easily reusable. I also like the car analogy that you used to explain the difference between a relational database and an object oriented one. Thanks for reading and commenting on my post as well!