awaneeshp wrote
Hello,
I wanted to know what are the advantages i would be having with me if ill go ahead & use a webservice within DNN frmawork.
In my case, if i develop a webservice then it will be just holding web methods to redirect to specif dataaccess layer class & the business logic is going to reside with stored proc which i think can be done easily within DNN framework.
Also, I have a situation where in i need to call external interfaces (that could be a webservice) to get data & merge that data with the data from my DB server & then send it to UI. Now, Is it required that i need to get this done using webservices within DNN ? OR Can this be done within DNN dataaccess layer class without writing any web services.
Which way is more flexible & scalable to use?
Please suggest me to take this architectural decision as i m a newbie to DNN architectural framework.
Thanks,
-Awaneesh
Well, often the descion is quite clear...
If you have a need to access to distributed data (calling DNN webservices from an external asp.net or winforms app, or calling external webservices from a DNN module to complete the business side of a module) then it makes sense to use the webservices (in certain situations).
If you are just thinking on distributing the architecture of a DNN module to provide a cleaner boundary between a DNN module and it's database (SOA like fashion), then using web services to achive this is an overhead.
Can you give us a more concrete example of what you want to do?