Architecture

Groxx — Thu, 24 Feb 2011 00:50:31 GMT

Current revision posted to NHibernate 2.0 by Groxx on 23/02/2011 09:50:31 p.m.

Architecture

Filed under: Architecture, Session, SessionFactory, Architecture

Wiki extracted from the 2.0 Reference Documentation

Overview

A (very) high-level view of the NHibernate architecture:

This diagram shows NHibernate using the database and configuration data to provide persistence services (and persistent objects) to the application.

We would like to show a more detailed view of the runtime architecture. Unortunately, NHibernate is flexible and supports several approaches. We will show the two extremes. The "lite" architecture has the application provide its own ADO.NET connections and manage its own transactions. This approach uses a minimal subset of NHibernate's APIs:

The "full cream" architecture abstracts the application away from the underlying ADO.NET APIs and lets NHibernate take care of the details.

Here some definitions of the objects in the diagrams:

ISessionFactory (NHibernate.ISessionFactory)

A threadsafe (immutable) cache of compiled mappings for a single database. A factory for ISession and a client of IConnectionProvider. Might hold an optional (second-level) cache of data that is reusable between transactions, at a process- or cluster-level.

ISession (NHibernate.ISession)

A single-threaded, short-lived object representing a conversation between the application and the persistent store. Wraps an ADO.NET connection. Factory for ITransaction. Holds a mandatory (first-level) cache of persistent objects, used when navigating the object graph or looking up objects by identifier.

Persistent Objects and Collection

Short-lived, single threaded objects containing persistent state and business function. These might be ordinary POCOs (Plain Old CLR Objects), the only special thing about them is that they are currently associated with (exactly one) ISession. As soon as the Session is closed, they will be detached and free to use in any application layer (e.g. directly as data transfer objects to and from presentation).

Transient Objects and Collections

Instances of persistent classes that are not currently associated with a ISession. They may have been instantiated by the application and not (yet) persisted or they may have been instantiated by a closed ISession.

ITransaction (NHibernate.ITransaction)

(Optional) A single-threaded, short-lived object used by the application to specify atomic units of work. Abstracts application from underlying ADO.NET transaction. An ISession might span several ITransactions in some cases.

IConnectionProvider (NHibernate.Connection.IConnectionProvider)

(Optional) A factory for ADO.NET connections and commands. Abstracts application from the concrete vendor-specific implementations of IDbConnection and IDbCommand. Not exposed to application, but can be extended/implemented by the developer.

IDriver (NHibernate.Driver.IDriver)

(Optional) An interface encapsulating differences between ADO.NET providers, such as parameter naming conventions and supported ADO.NET features.

ITransactionFactory (NHibernate.Transaction.ITransactionFactory)

(Optional) A factory for ITransaction instances. Not exposed to the application, but can be extended/implemented by the developer.

Given a "lite" architecture, the application bypasses the ITransaction, ITransactionFactory and/or IConnectionProvider APIs to talk to ADO.NET directly.

Architecture

Groxx — Thu, 24 Feb 2011 00:49:12 GMT

Revision 9 posted to NHibernate 2.0 by Groxx on 23/02/2011 09:49:12 p.m.

Architecture

Filed under: Session, SessionFactory, Architecture

Wiki extracted from the 2.0 Reference Documentation

Overview

A (very) high-level view of the NHibernate architecture:

This diagram shows NHibernate using the database and configuration data to provide persistence services (and persistent objects) to the application.

We would like to show a more detailed view of the runtime architecture. FortunatelyUnortunately, NHibernate is flexible and supports several approaches. We will show the two extremes. The "lite" architecture has the application provide its own ADO.NET connections and manage its own transactions. This approach uses a minimal subset of NHibernate's APIs:

The "full cream" architecture abstracts the application away from the underlying ADO.NET APIs and lets NHibernate take care of the details.

Here some definitions of the objects in the diagrams:

ISessionFactory (NHibernate.ISessionFactory)

ISession (NHibernate.ISession)

Persistent Objects and Collection

Short-lived, single threaded objects containing persistent state and business function. These might be ordinary POCOs, the only special thing about them is that they are currently associated with (exactly one) ISession. As soon as the Session is closed, they will be detached and free to use in any application layer (e.g. directly as data transfer objects to and from presentation).

Transient Objects and Collections

ITransaction (NHibernate.ITransaction)

IConnectionProvider (NHibernate.Connection.IConnectionProvider)

IDriver (NHibernate.Driver.IDriver)

(Optional) An interface encapsulating differences between ADO.NET providers, such as parameter naming conventions and supported ADO.NET features.

ITransactionFactory (NHibernate.Transaction.ITransactionFactory)

(Optional) A factory for ITransaction instances. Not exposed to the application, but can be extended/implemented by the developer.

Given a "lite" architecture, the application bypasses the ITransaction, ITransactionFactory and/or IConnectionProvider APIs to talk to ADO.NET directly.

Architecture

Groxx — Thu, 24 Feb 2011 00:16:07 GMT

Revision 8 posted to NHibernate 2.0 by Groxx on 23/02/2011 09:16:07 p.m.

Architecture

Filed under: Session, SessionFactory, Architecture

Overview

A (very) high-level view of the NHibernate architecture:

This diagram shows NHibernate using the database and configuration data to provide persistence services (and persistent objects) to the application.

We would like to show a more detailed view of the runtime architecture. UnfortunatelyFortunately, NHibernate is flexible and supports several approaches. We will show the two extremes. The "lite" architecture has the application provide its own ADO.NET connections and manage its own transactions. This approach uses a minimal subset of NHibernate's APIs:

The "full cream" architecture abstracts the application away from the underlying ADO.NET APIs and lets NHibernate take care of the details.

Here some definitions of the objects in the diagrams:

ISessionFactory (NHibernate.ISessionFactory)

ISession (NHibernate.ISession)

Persistent Objects and Collection

Transient Objects and Collections

ITransaction (NHibernate.ITransaction)

IConnectionProvider (NHibernate.Connection.IConnectionProvider)

IDriver (NHibernate.Driver.IDriver)

(Optional) An interface encapsulating differences between ADO.NET providers, such as parameter naming conventions and supported ADO.NET features.

ITransactionFactory (NHibernate.Transaction.ITransactionFactory)

(Optional) A factory for ITransaction instances. Not exposed to the application, but can be extended/implemented by the developer.

Given a "lite" architecture, the application bypasses the ITransaction, ITransactionFactory and/or IConnectionProvider APIs to talk to ADO.NET directly.

Architecture

Fabio Maulo — Fri, 05 Sep 2008 23:28:53 GMT

Revision 7 posted to NHibernate 2.0 by Fabio Maulo on 05/09/2008 08:28:53 p.m.

Architecture

Filed under: Session, SessionFactory, Architecture

Overview

A (very) high-level view of the NHibernate architecture:

This diagram shows NHibernate using the database and configuration data to provide persistence services (and persistent objects) to the application.

We would like to show a more detailed view of the runtime architecture. Unfortunately, NHibernate is flexible and supports several approaches. We will show the two extremes. The "lite" architecture has the application provide its own ADO.NET connections and manage its own transactions. This approach uses a minimal subset of NHibernate's APIs:

The "full cream" architecture abstracts the application away from the underlying ADO.NET APIs and lets NHibernate take care of the details.

Here some definitions of the objects in the diagrams:

ISessionFactory (NHibernate.ISessionFactory)

ISession (NHibernate.ISession)

Persistent Objects and Collection

Transient Objects and Collections

ITransaction (NHibernate.ITransaction)

IConnectionProvider (NHibernate.Connection.IConnectionProvider)

IDriver (NHibernate.Driver.IDriver)

(Optional) An interface encapsulating differences between ADO.NET providers, such as parameter naming conventions and supported ADO.NET features.

ITransactionFactory (NHibernate.Transaction.ITransactionFactory)

(Optional) A factory for ITransaction instances. Not exposed to the application, but can be extended/implemented by the developer.

Given a "lite" architecture, the application bypasses the ITransaction, ITransactionFactory and/or IConnectionProvider APIs to talk to ADO.NET directly.

Architecture

Fabio Maulo — Fri, 05 Sep 2008 23:28:53 GMT

Revision 6 posted to NHibernate 2.0 by Fabio Maulo on 05/09/2008 08:28:53 p.m.

Architecture

Overview

A (very) high-level view of the NHibernate architecture:

This diagram shows NHibernate using the database and configuration data to provide persistence services (and persistent objects) to the application.

The "full cream" architecture abstracts the application away from the underlying ADO.NET APIs and lets NHibernate take care of the details.

Here some definitions of the objects in the diagrams:

ISessionFactory (NHibernate.ISessionFactory)

ISession (NHibernate.ISession)

Persistent Objects and Collection

Transient Objects and Collections

ITransaction (NHibernate.ITransaction)

IConnectionProvider (NHibernate.Connection.IConnectionProvider)

IDriver (NHibernate.Driver.IDriver)

(Optional) An interface encapsulating differences between ADO.NET providers, such as parameter naming conventions and supported ADO.NET features.

ITransactionFactory (NHibernate.Transaction.ITransactionFactory)

(Optional) A factory for ITransaction instances. Not exposed to the application, but can be extended/implemented by the developer.

Given a "lite" architecture, the application bypasses the ITransaction, ITransactionFactory and/or IConnectionProvider APIs to talk to ADO.NET directly.

Architecture

Fabio Maulo — Sun, 31 Aug 2008 23:25:03 GMT

Revision 5 posted to NHibernate 2.0 by Fabio Maulo on 31/08/2008 08:25:03 p.m.

Architecture

Overview

A (very) high-level view of the NHibernate architecture:

This diagram shows NHibernate using the database and configuration data to provide persistence services (and persistent objects) to the application.

The "full cream" architecture abstracts the application away from the underlying ADO.NET APIs and lets NHibernate take care of the details.

Here some definitions of the objects in the diagrams:

ISessionFactory (NHibernate.ISessionFactory)

ISession (NHibernate.ISession)

Persistent Objects and Collection

Transient Objects and Collections

ITransaction (NHibernate.ITransaction)

IConnectionProvider (NHibernate.Connection.IConnectionProvider)

IDriver (NHibernate.Driver.IDriver)

(Optional) An interface encapsulating differences between ADO.NET providers, such as parameter naming conventions and supported ADO.NET features.

ITransactionFactory (NHibernate.Transaction.ITransactionFactory)

(Optional) A factory for ITransaction instances. Not exposed to the application, but can be extended/implemented by the developer.

Given a "lite" architecture, the application bypasses the ITransaction, ITransactionFactory and/or IConnectionProvider APIs to talk to ADO.NET directly.

Architecture

Fabio Maulo — Sun, 31 Aug 2008 23:25:03 GMT

Revision 4 posted to NHibernate 2.0 by Fabio Maulo on 31/08/2008 08:25:03 p.m.

Architecture

Overview

A (very) high-level view of the NHibernate architecture:

This diagram shows NHibernate using the database and configuration data to provide persistence services (and persistent objects) to the application.

The "full cream" architecture abstracts the application away from the underlying ADO.NET APIs and lets NHibernate take care of the details.

Here some definitions of the objects in the diagrams:

ISessionFactory (NHibernate.ISessionFactory)

ISession (NHibernate.ISession)

Persistent Objects and Collection

Transient Objects and Collections

ITransaction (NHibernate.ITransaction)

IConnectionProvider (NHibernate.Connection.IConnectionProvider)

IDriver (NHibernate.Driver.IDriver)

(Optional) An interface encapsulating differences between ADO.NET providers, such as parameter naming conventions and supported ADO.NET features.

ITransactionFactory (NHibernate.Transaction.ITransactionFactory)

(Optional) A factory for ITransaction instances. Not exposed to the application, but can be extended/implemented by the developer.

Given a "lite" architecture, the application bypasses the ITransaction, ITransactionFactory and/or IConnectionProvider APIs to talk to ADO.NET directly.

Architecture

Fabio Maulo — Sun, 31 Aug 2008 23:25:03 GMT

Revision 3 posted to NHibernate 2.0 by Fabio Maulo on 31/08/2008 08:25:03 p.m.

Architecture

Overview

A (very) high-level view of the NHibernate architecture:

This diagram shows NHibernate using the database and configuration data to provide persistence services (and persistent objects) to the application.

The "full cream" architecture abstracts the application away from the underlying ADO.NET APIs and lets NHibernate take care of the details.

Here some definitions of the objects in the diagrams:

ISessionFactory (NHibernate.ISessionFactory)

ISession (NHibernate.ISession)

Persistent Objects and Collection

Transient Objects and Collections

ITransaction (NHibernate.ITransaction)

IConnectionProvider (NHibernate.Connection.IConnectionProvider)

IDriver (NHibernate.Driver.IDriver)

(Optional) An interface encapsulating differences between ADO.NET providers, such as parameter naming conventions and supported ADO.NET features.

ITransactionFactory (NHibernate.Transaction.ITransactionFactory)

(Optional) A factory for ITransaction instances. Not exposed to the application, but can be extended/implemented by the developer.

Given a "lite" architecture, the application bypasses the ITransaction, ITransactionFactory and/or IConnectionProvider APIs to talk to ADO.NET directly.

Architecture

Fabio Maulo — Sun, 31 Aug 2008 23:24:38 GMT

Revision 2 posted to NHibernate 2.0 by Fabio Maulo on 31/08/2008 08:24:38 p.m.

Architecture

Overview

A (very) high-level view of the NHibernate architecture:

This diagram shows NHibernate using the database and configuration data to provide persistence services (and persistent objects) to the application.

The "full cream" architecture abstracts the application away from the underlying ADO.NET APIs and lets NHibernate take care of the details.

Here some definitions of the objects in the diagrams:

ISessionFactory (<tt>NHibernate.ISessionFactory</tt>) </dt><dd> NHibernate.ISessionFactory)

A threadsafe (immutable) cache of compiled mappings for a single database. A factory for <tt>ISession</tt> ISession and a client of <tt>IConnectionProvider</tt>. IConnectionProvider. Might hold an optional (second-level) cache of data that is reusable between transactions, at a process- or cluster-level.

</dd><dt>

ISession (<tt>NHibernate.ISession</tt>) </dt><dd> NHibernate.ISession)

A single-threaded, short-lived object representing a conversation between the application and the persistent store. Wraps an ADO.NET connection. Factory for <tt>ITransaction</tt>. ITransaction. Holds a mandatory (first-level) cache of persistent objects, used when navigating the object graph or looking up objects by identifier.

</dd><dt>

Persistent Objects and Collections </dt><dd> Collection

Short-lived, single threaded objects containing persistent state and business function. These might be ordinary POCOs, the only special thing about them is that they are currently associated with (exactly one) <tt>ISession</tt>. ISession. As soon as the <tt>Session</tt> Session is closed, they will be detached and free to use in any application layer (e.g. directly as data transfer objects to and from presentation).

</dd><dt>

Transient Objects and Collections </dt><dd>

Instances of persistent classes that are not currently associated with a <tt>ISession</tt>. ISession. They may have been instantiated by the application and not (yet) persisted or they may have been instantiated by a closed <tt>ISession</tt>.

</dd><dt>ISession.

ITransaction (<tt>NHibernate.ITransaction</tt>) </dt><dd> NHibernate.ITransaction)

(Optional) A single-threaded, short-lived object used by the application to specify atomic units of work. Abstracts application from underlying ADO.NET transaction. An <tt>ISession</tt> ISession might span several <tt>ITransaction</tt>s ITransactions in some cases.

</dd><dt>

IConnectionProvider (<tt>NHibernate.Connection.IConnectionProvider</tt>) </dt><dd> NHibernate.Connection.IConnectionProvider)

(Optional) A factory for ADO.NET connections and commands. Abstracts application from the concrete vendor-specific implementations of <tt>IDbConnection</tt> IDbConnection and <tt>IDbCommand</tt>. IDbCommand. Not exposed to application, but can be extended/implemented by the developer.

</dd><dt>

IDriver (<tt>NHibernate.Driver.IDriver</tt>) </dt><dd> NHibernate.Driver.IDriver)

(Optional) An interface encapsulating differences between ADO.NET providers, such as parameter naming conventions and supported ADO.NET features.

</dd><dt>

ITransactionFactory (<tt>NHibernate.Transaction.ITransactionFactory</tt>) </dt><dd> NHibernate.Transaction.ITransactionFactory)

(Optional) A factory for <tt>ITransaction</tt> ITransaction instances. Not exposed to the application, but can be extended/implemented by the developer.

</dd></dl>

Given a "lite" architecture, the application bypasses the <tt>ITransaction</tt>/<tt>ITransactionFactory</tt> ITransaction, ITransactionFactory and/or <tt>IConnectionProvider</tt> IConnectionProvider APIs to talk to ADO.NET directly.

Architecture

Fabio Maulo — Sun, 31 Aug 2008 23:18:37 GMT

Revision 1 posted to NHibernate 2.0 by Fabio Maulo on 31/08/2008 08:18:37 p.m.

Overview

A (very) high-level view of the NHibernate architecture:

This diagram shows NHibernate using the database and configuration data to provide persistence services (and persistent objects) to the application.

The "full cream" architecture abstracts the application away from the underlying ADO.NET APIs and lets NHibernate take care of the details.

Here some definitions of the objects in the diagrams:

<dl> <dt>ISessionFactory (<tt>NHibernate.ISessionFactory</tt>) </dt><dd>

A threadsafe (immutable) cache of compiled mappings for a single database. A factory for <tt>ISession</tt> and a client of <tt>IConnectionProvider</tt>. Might hold an optional (second-level) cache of data that is reusable between transactions, at a process- or cluster-level.

</dd><dt>ISession (<tt>NHibernate.ISession</tt>) </dt><dd>

A single-threaded, short-lived object representing a conversation between the application and the persistent store. Wraps an ADO.NET connection. Factory for <tt>ITransaction</tt>. Holds a mandatory (first-level) cache of persistent objects, used when navigating the object graph or looking up objects by identifier.

</dd><dt>Persistent Objects and Collections </dt><dd>

Short-lived, single threaded objects containing persistent state and business function. These might be ordinary POCOs, the only special thing about them is that they are currently associated with (exactly one) <tt>ISession</tt>. As soon as the <tt>Session</tt> is closed, they will be detached and free to use in any application layer (e.g. directly as data transfer objects to and from presentation).

</dd><dt>Transient Objects and Collections </dt><dd>

Instances of persistent classes that are not currently associated with a <tt>ISession</tt>. They may have been instantiated by the application and not (yet) persisted or they may have been instantiated by a closed <tt>ISession</tt>.

</dd><dt>ITransaction (<tt>NHibernate.ITransaction</tt>) </dt><dd>

(Optional) A single-threaded, short-lived object used by the application to specify atomic units of work. Abstracts application from underlying ADO.NET transaction. An <tt>ISession</tt> might span several <tt>ITransaction</tt>s in some cases.

</dd><dt>IConnectionProvider (<tt>NHibernate.Connection.IConnectionProvider</tt>) </dt><dd>

(Optional) A factory for ADO.NET connections and commands. Abstracts application from the concrete vendor-specific implementations of <tt>IDbConnection</tt> and <tt>IDbCommand</tt>. Not exposed to application, but can be extended/implemented by the developer.

</dd><dt>IDriver (<tt>NHibernate.Driver.IDriver</tt>) </dt><dd>

(Optional) An interface encapsulating differences between ADO.NET providers, such as parameter naming conventions and supported ADO.NET features.

</dd><dt>ITransactionFactory (<tt>NHibernate.Transaction.ITransactionFactory</tt>) </dt><dd>

(Optional) A factory for <tt>ITransaction</tt> instances. Not exposed to the application, but can be extended/implemented by the developer.

</dd></dl>

Given a "lite" architecture, the application bypasses the <tt>ITransaction</tt>/<tt>ITransactionFactory</tt> and/or <tt>IConnectionProvider</tt> APIs to talk to ADO.NET directly.