WCF Domain Model for SOA Part – 1

Hallo folks … see you again in my sharing knowledge moment in my
development journal blogs,
i would like to share to all of you about the knowledge of creating the
domain architecture,
in this case i would like to create the WCF ( Windows Communication
Foundation ) especially for further purpose is
implement the SOA ( Software Oriented Architecture ).

I will separate the part of the knowledge become the trilogy knowledge
which are :

1. Introduction the Domain WCF or Web service
2. Introduction the Service Factory from The Pattern and Practise team to implement the WCF or Web service as a Domain Artifact model.
3. Sample implementation the WCF or Web service.

so..let’s try to rock’n roll …

Overview :
the application development in this era has already come to service
oriented architecture which is known by SOA, by using SOA
we implement the interoperability application architecture which avoid
the system operation platform or even the language
of application development and domain application as well. we using the
independence file format transferring or independence format that
allow every domain
application could leverage every programming functionality such as
procedure or method for IPO ( Input-Process-Output) processing
Because the original purpose of SOA is become a bridge of many platform
which cater the functionality of the application then the ser-
vice need the endpoint or even the contract which is tighten from one
service point to another service point or from one domain
application to another domain application but of course loosely
coupling architecture.

For further detail explanation i put some figure about the domain WCF :

Domain model provide the abstraction and also the entity relationship
between the environment
application that we can assume like the glosary between a word. let’s
take a look the main things of this
model :

• Service contract is the abstract things in the web CLR or interface. service implementation is looks like the concrete class that implements the interface.
• service host is somekind a the host the service or like an actor that catering the service.
• the service host invoke the service implementation and then the service implementation invoke based on the service contract which is showed by the dash arrow connector.

Next we will talk about the contract element area here there are :

• The Service contract is the nomenclature of way that we think about service application which is ,
• The service contract has a method operation which has purpose to pass the request and respond the message in two way direction or one way direction in thedomain, not only the message that will be delivered but also the data type such as customer datatype and so on.
• and then finaly the fault contract is the exception handling services in the application which has a service to throw the exception and handling the failure message.

For the functionality area, it’s figure the implementation
functionality and it’s looks
like the abstraction and not the concrete technology implementation
inside, i will explain
the mechanism like the following step :

• The service implementation has a service adapter that become a bridge between outside world domain and the inside, this service adapter has a funtion such as business facade interface controller from the service domain.
• The business facade controller contain or using the business  component application and business entity which is different than the datacontract, the business component has the funtion as well for being the translator from the datacontract inside the business application and also the data from the outside world, the translator is somekind like the serialization or deserialization mechanism.

as i told to you at the beginning overview that the service will talk
to another service or even
another application domain,that’s why the service has the connectivity
channel in this case
binding is talking about the media that service want to talk and the
endpoint is the point that
become the initial talking point or become the destination point. The
binding way platform
could use the Http way, channel IP adress remoting way ,the COM+
interface or by using the SOAP messaging
protocol. that’s why
the WCF leverage manykind of transport method and enhance the previous
platform SOA which was
catered by the web service and also the COM+ technology.

The lasthing that, due to the service will process in the independent
format but still need to keep maintain the
quality of the service in each platform, which is suppose tobe separate
from the it’s service and the operating system
service such as respond time service , attaching the format through the
binding and also availability supporting format
that the application didn’t care about that because it’s become the OS
job.

i guess my explanation is quite enough to understand the model of WCF
domain and next we will meet in the tools that we could
applied those bunch theory above.

See you in my next article…

Regards,
Doddy Ch saputra

---

Possibly related posts: (automatically generated)

• SharePoint Conference 2009: Service Applications
• Web Services
• Service Oriented Architecture (SOA)
• IBM takes a swipe at Google with Web-based e-mail