preview

Database Vs. Relational Database Model

Decent Essays

One size fits all. The developers go to for all data. You need only a relational database. This is the false assumption that you will see when it comes to database models. The relational database model is great for data that normally can fit into a table, or shows relationships between data, but not all data falls into that category. There are a few options for these situations. You can use an object-oriented database, a hierarchical database, a network database, and a flat-file database. The first alternative is known as the object-oriented. In a document-oriented database model, each individual record, and all of the data associated with that record, is thought of as a document. In this type of database, everything that is related to a database object, or document, is grouped together. This keeps the database organized, and easier to find things that are related to each other. Each document is encoding data in some format or encoding. The most common formats include XML, JSON and BSON. These are just some of the formats available, but these seem to be the most popular formats that are being used.
A document can have single, or even multiple fields. These fields can vary from document to document, which gives each document a lot of flexibility. There is no need to worry about constraints, like we see in our relational database, but validation documents can be made to enforce rules as needed. This type of database can typically accept multiple languages, instead of just

Get Access