Exposing BL as WCF service
Posted
by
Oren Schwartz
on Server Fault
See other posts from Server Fault
or by Oren Schwartz
Published on 2011-11-27T00:02:30Z
Indexed on
2011/11/27
1:52 UTC
Read the original article
Hit count: 695
I'm working on a middle-tier project which encapsulates the business logic (uses a DAL layer, and serves a web application server [ASP.net]) of a product deployed in a LAN. The BL serves as a bunch of services and data objects that are invoked upon user action.
At present times, the DAL acts as a separate application whereas the BL uses it, but is consumed by the web application as a DLL. Both the DAL and the web application are deployed on different servers inside organization, and since the BL DLL is consumed by the web application, it resides in the same server.
The worst thing about exposing the BL as a DLL is that we lost track with what we expose. Deployment is not such a big issue since mostly, product versions are deployed together.
Would you recommend migrating from DLL to WCF service? if so, why ? Do you know anyone who had a similar experience ?
© Server Fault or respective owner