| Long Form | Stands for Relational Database Management System. | Stands for Object Oriented Database Management System. |
|---|
| Way of storing data | Stores data in Entities, defined as tables hold specific information. | Stores data as Objects. |
|---|
| Data Complexity | Handles comparatively simpler data. | Handles larger and complex data than RDBMS. |
|---|
| Grouping | Entity type refers to the collection of entity that share a common definition. | Class describes a group of objects that have common relationships, behaviors, and also have similar properties. |
|---|
| Data Handling | RDBMS stores only data. | Stores data as well as methods to use it. |
|---|
| Main Objective | Data Independence from application program. | Data Encapsulation. |
|---|
| Key | A Primary key distinctively identifies an object in a table. | An object identifier (OID) is an unambiguous, long-term name for any type of object or entity. |
|---|
| Data Retrieval | SQL (Structured Query Language) | Object Query Language (OQL) |
|---|
| Scalability | RDBMS has Limited scalability due to rigid schema | OODBMS has Highly scalable due to flexible schema |
|---|
| Concurrency Control | RDBMS has Fine-grained locking | OODBMS has Optimistic concurrency control |
|---|
| Data Relationships | In RDBMS Relational data is stored in tables and linked via foreign keys | In OODBMS, data is stored as objects linked via object references instead of foreign keys. |
|---|
| Performance | RDBMS is Efficient for complex queries involving multiple tables | OODBMS is Faster for complex object-oriented queries |
|---|
| Flexibility | RDBMS has Limited flexibility due to fixed schema | OODBMS has highly flexible due to object-oriented nature |
|---|
| Data Persistence | In RDBMS Data is stored in tables on disk | In OODBMS Data is stored in objects in memory or on disk |
|---|
| Examples | MySQL, Oracle, SQL Server | db4o, Versant, Objectivity/DB |
|---|