.net - why not reference wcf service from web project? -
in traditional way of thinking (remember dna?) we're supposed architect our application separating layers services. when implementing asp.net mvc application, why should implement service , wrap wcf references separate dll, rather having web application reference wcf directly?
i can think of 2 arguments, , thoughts on those:
- keep code in once place (well, still done when have wcf!)
- reusable service when other systems need service (well, if internal application?)
on other hand, people might argument over-architecture implementing alot of layers bring more complexity solution , not yield benefits expected.
i'm not fan of introducing dlls "because". been there; ot t-shirt dependency graph on it. if can't define benefit in environment/context, simplest thing - may reference web app.
i've heard argument of allowing re-use, counter: soap/mex pretty-much defining this. argument testability, isolation, separation etc; , depends on how benefit these give you (or rather: team) in your usage.
one very valid case separate dll here when (mainly internal apps) sharing dto library between wcf server , client, both have rich objects rather simple shadows. bit gather (from tone) doesnt apply in case.
Comments
Post a Comment