WebSphere Commerce Data Services Layer

In my last post, I introduced concepts and layers around the BOD framework.  Now I plan to dig a little more into the framework and discuss an important layer within the framework, DSL.

The WebSphere Commerce BOD framework often refers to the data services layer (DSL).  For those familiar with the NVP command programming model, the DSL replaces the EJBs and Access Beans.  It provides the abstract layer for data access decoupled from the physical database schema.  I am going to try to pull some of the information together for a decent overview of DSL.

Here is a high level view from the info center of where in the architecture the DSL fits in.

BOD, What is it? Should I use it?

WebSphere Commerce BOD, this architecture in WCS is not as straight forward to follow at first, unlike the NVP Command framework.  As WebSphere Commerce is transitioning to SOA, there is a need to ensure decoupling of the various components and allow re-use of the WebSphere Commerce business services. The result is a change to the frameworks driving development within WCS.  This is where the BOD framework comes in.

So what is BOD?