Terminology: "Entity Bean" and "Data Model"

We're in a conversation where one developer uses the term "Entity Bean" and one describes something relatively similar to the "Data Model" .

Are these terms synonymous? Are there subtle differences from terms that should be considered?

The environment is PHP, with some ex-java files belonging to developers.


source to share

3 answers

This is completely different.

A bean is an in-memory representation of a single item of data, usually from a database. This term is also used for the class to which the bean belongs.

The Physical Data Model is a schema for expressing a range of different types of data in database tables. The Logical Data Model is sort of an abstract version. But none of them look like an entity bean.



Both are different.

Essence Bean:

This is a component of the ORM, it is the part of the EJB that handles database transactions.

Data model:

This name is given to the operations that will be performed on the database. There are many other ORM tools that go into data model programming like (Hibernate, springs and EJB).


A data model is a collection of classes that are created as a framework for performing database operations.



Bean and Data Model are not synonymous. A Bean is a class that maps to a table (or set of tables) in the Data Model.

Typically, a data model represents data and relationships between data to support the persistence requirements of an application.

An application usually consists of classes that represent and process data according to the business rules defined in the class methods.

The beans will be the class used to maintain persistent data, and will generally be tightly bound to the tables in the data model.



All Articles