c# - Should I put customer specific requirements for an API into the BLL layer? -


i have build small app wcf api crud operations database. want create dal --> bll --> web service layer in order.

in dal intend create basic table crud operations db on 1 1 basis, 1 call 1 operation on table.

one of requirents legacy app uses interface needs have access wcf webservices each screen have associated web service method. i.e. screen (which business decide have 1 single method serve each screen).

im wondering should build these requirements bll, , re-expose via webservices? or should create bll logical business operations , build facade on top create specific (screen web method call requirment mentioned above) , re-expose on wcf instead?

i dont want overcomplicate app want extensible obviously.

any advice apreciated.

in general, think makes sense keep bll clean , usable else needs it. then, if need support legacy calls, idea of facade one. allow bll stay way should, while facade orchestrate correct/existing bll logic serve legacy app.

it's cheap way out answer way. answer agree you; build facade support legacy calls , orchestrate existing bll api calls. way bll stays clean.


Comments

Popular posts from this blog

javascript - backbone.js Collection.add() doesn't `construct` (`initialize`) an object -

php - Get uncommon values from two or more arrays -

Adding duplicate array rows in Php -