View source for Implementing Domain Driven Architecture with OSGi

From Opentaps Wiki

← Implementing Domain Driven Architecture with OSGi

You do not have permission to edit this page, for the following reasons:

• The action you have requested is limited to users in the group: Users.
• This page has been protected to prevent editing or other actions.

---

You can view and copy the source of this page.

''This document is not finished yet.'' == Goals == Move data model out of the database to the middleware tier. Mixed data sources -- cloud or database. Segregate the applications by segregating the data model. Prevent bloated software by making it truly modular: no unnecessary dependencies between modules. == Concepts == Domain classes are the '''nouns''': a Person, a Product, an Order. Services are '''verbs''': CreateOrder, UpdateProduct. They create or modify the domain classes. Services should be used as [http://helephant.com/2008/08/19/functions-are-first-class-objects-in-javascript/ first class objects] and passed around to perform these actions. == Rules == No foreign keys between domains (ie, OrderItem.productId should not FK to Product.productId). The Product data source might not be your database!

Return to Implementing Domain Driven Architecture with OSGi.