All geek questions in one place

Can a SQL Server 2008 database support both REST and SOAP web services at two different endpoints?

Say you have a SQL Server 2008 database. You are creating a SOAP web service. You then deploy or publish this using Visual Studio 2010 on one website. Now, using the same database, you create the REST web service in a different solution. You are deploying this on another website.

Can you use endpoints and / or .svc file for both SOAP and REST web services, although they all refer to the same SQL Server 2008 database?

I don’t understand why not, but before I go this route and spend the days, I would like to make sure.

Also, if there is performance in the database, if it launches SOAP and REST at the same time - again, I don’t understand why this matters, but I have to make sure. Thanks.

+4
source share
2 answers

SQL Server does not know anything about your web service - it will simply receive requests and return the data to the calling connection (in this case, your server code).

It doesn’t matter if the request came up in VBA, Mgmt Studio, your SOAP service, or all three.

+1
source

The database does not completely pay attention to how your customers send requests. All he sees is ODBC (or something else) connections that make requests. You can have 20 people sitting in SQL Developer, typing these queries manually, this will not know anything better. So, you are right, your question does not make sense - you can have as many different interfaces as you want, performance / loading will be determined only by completed requests.

+2
source

Source: https://habr.com/ru/post/1381170/

More articles:


All Articles