WCF service vs Code behind - Performance and Re-usability tradeoffs

Question

0.00/5 (No votes)

See more:

For a task such as updating the SQL Database, what are the performance and re-usability trade-offs between the two approaches mentioned below?

1. WCF Service for "update the SQL tables" task. And then calling it from ASP.Net Web Application.
2. "Updating the SQL" table using ADO.Net from ASP.Net Web Application code-behind.

I'm looking for an analysis on user and implementation point of view.
Please note that the activity is one time per user. Also, we are looking for a solution which can be re-used.

I know this is more of a debate than asking for a solution, but appreciate the responses.

Cheers,
Naman

Posted 7-Jan-14 18:46pm

Naman Kumar Sinha

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

thatraja · Answer 1 · 2014-01-08T01:48:00

Quote:
Database, what are the performance and re-usability trade-offs between the two approaches mentioned below?

1. WCF Service for "update the SQL tables" task. And then calling it from ASP.Net Web Application.
2. "Updating the SQL" table using ADO.Net from ASP.Net Web Application code-behind.

Go with 1st option.
0) By using Webservice(WCF), you could reuse the same things when end-user/you want to go with other targets(like Winform, WPF/Silverlight, etc.,). There's no need to rewrite things. All you have to do is call the service, that's it.
1) Easy deployment things
2) You could optimize your services too[^]
3) Consider you have written some code in your code-behind, what'll you do if you want to call the samething from multiple pages/projects? Copy-paste on multiple places?X| Here Webservice rocks, just call the service URL.
4) And you could secure things(restrict-others to use methods) by implementing authentication +/ authorization at service level.
5) There're more .... just Google for webservice/wcf advantages.