Can we use database with web services

Question

1.00/5 (2 votes)

See more:

Can we use database in web services means can we connect database with web service? or we have to used database only with our web app and use with web services when web services called.

Posted 27-Jan-16 20:17pm

Kishor-KW

Add a Solution

Comments

Sergey Alexandrovich Kryukov 28-Jan-16 2:30am

Multi-tier.
—SA

Mohibur Rashid 28-Jan-16 3:32am

agreed

Kishor-KW 28-Jan-16 4:16am

web service is at the top here, right?

Sergey Alexandrovich Kryukov 28-Jan-16 9:04am

No.
—SA

2 solutions

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)

ZurdoDev · Answer 1 · 2016-01-28T01:38:00

Solution 1

Yes, you can connect to a database via web services. But it depends on the db and you may have to write all the code yourself if an interface does not currently exist.

Posted 28-Jan-16 1:38am

ZurdoDev

Sergey Alexandrovich Kryukov · Answer 2 · 2016-01-28T04:45:00

Top, bottom… what are you talking about? What options you may possibly have?

Let's say, you have a database server with a database. Let's say this is your back-end data tier. You can have another tier, running your WCF service. It can use different hosting (IIS, self-host…), different protocols — this is the whole idea behind WCF, but your application-layer protocol in on you, it can be expressed in the form your you WCF service contract. You can have many options here. Your contract can be close to the database semantics, or it can abstract out functional detail of your particular database service and present some more generalized database model. Or it can reflect just the semantics of your application. Or you can combine those approaches. And you can have more than one WCF service. Your service application should play the role of the WCF and, from the other hand, should act as a client of your database.

And then you can have anything else you need, but the idea is: your other tier(s) will communicate to the database only through your WCF tier.

Please see: Multitier architecture - Wikipedia, the free encyclopedia[^].

—SA