 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / Languages / C# / April 2008Service Oriented Architecture
I'm in the process of designing a Service Oriented Architecture. At the moment I based the design on the Web Service Software factory guidelines - so a services layer, business layer and resource access layer. The services layer contains WCF services, which use the business layer, which uses the resource access layer. I'm using data contracts for data that is passed via the WCF services, and these are converted to business entitities that pass to business layer and data layer. Meanwhile the data layer has become a WCF service. So, the question arise: how do I pass the data now? Even further: imagine that I would make everything a service, how would you pass data between tiers? Can I define internal data contracts once, and use these over all WCF services for example? Or how would the best approach be - if every service uses its own data contract then I need to convert everything in every service and I think that's overkill? > I'm in the process of designing a Service Oriented Architecture. At > the moment I based the design on the Web Service Software factory [quoted text clipped - 4 lines] > converted to business entitities that pass to business layer and data > layer. Sounds very fine. > Meanwhile the data layer has become a WCF service. So, the question > arise: how do I pass the data now? Even further: imagine that I would [quoted text clipped - 4 lines] > service uses its own data contract then I need to convert everything > in every service and I think that's overkill? The approach is: don't ! SOA is about having systems provide a service at the business level to other systems. A data layer is not a business service. And a WCF interface to that is not SOA and with 98% probability a bad idea. Arne > ludwig_stu...@hotmail.com wrote: > > I'm in the process of designing a Service Oriented Architecture. At [quoted text clipped - 26 lines] > > Arne The reason to service enable (part of) the data layer was because I needed to service enable a single-threaded COM API, and using WCF it as rather easy to do (single concurrency service and making sure that everything is executed in the same thread). . >> ludwig_stu...@hotmail.com wrote: >>> I'm in the process of designing a Service Oriented Architecture. At [quoted text clipped - 26 lines] > as rather easy to do (single concurrency service and making sure that > everything is executed in the same thread). . It can be an OK solution for a specific problem. I am not COM knowledgeable enough to comment on the specifics. But I would not call it SOA. Because you are exposing data not a service. Arne Even if you want to expose all the Data layer as a WCF service, access to it should be restricted. Data Contract seems to be the correct way to communicate between services. > Even if you want to expose all the Data layer as a WCF service, > access to it should be restricted. > Data Contract seems to be the correct way to communicate between > services. Indeed, data contract. But only if I can share that data contract between the various web services, because I don't want to do conversion between data in each service! Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.