Database Reference
In-Depth Information
As long as all functional boundaries are precise and individual, business logic ( BL ) en-
capsulated within each application is transpired and comprehendible. It can be clearly sep-
arated from application resources and modeled/remodeled using platform-independent
means as there are no parasitic couplings between separated elements of business logic of
any kind. Every application presents public operations and related data models via stand-
ardized APIs using common notations, available for all involved parties in a comprehend-
ible way.
A number of communication protocols and exchange patterns have been reduced to reas-
onable minimum with well defined timeouts and compensation activities if there are occa-
sional miscommunications.
What we just described is a collection of services, as they should be designed from the be-
ginning. A service can be perceived as an application if a functional context permits this
without affecting Loose Coupling and Abstraction negatively.
The following two assumptions are distinctive:
Assumption 1 : Services have non-overlapping functional boundaries, encapsulat-
ing the logic that is specific only for this service.
Assumption 2 : Services allow you to access the service logic only via a publicly
available service contract, which is expressed using the canonical data model and
canonical expressions for capabilities. Canonical protocols complete the picture.
Search WWH ::




Custom Search