Naming of types when using an ORM

Question

I am working on a project where a number of types have the suffix "Instance".

For example, we have the concept of tabs in the application, so we have a TabInstance type.

To me this seems redundant and even confusing / wrong, as there is already the concept of an instance in OO terminology.

The system uses nHibernate as an ORM - I wonder if such a naming scheme is something that is typical in systems using ORMs, or is used or some other reason?

Answer 1

For example, we have the concept of tabs in the application, so we have a TabInstance type.

It seems as if you should have the type Tab instead of TabInstance.

Answer 2

yes get rid of them.