Last post Jul 24, 2017 01:59 PM by PatriceSc
Jul 10, 2017 04:58 PM|Chait|LINK
Am working on a web application(normal Asp.net and SQL server) where each user action need to be captured. Like search, edit , delete, login and logout. To reduce the load on the current DB and application, am planning to write down a separate web service/WCF/WebAPI
which will take all necessary parameters and writes into separate DB table to log all these data.
Can any one suggest which one is best approach or design architecture?
Jul 10, 2017 05:40 PM|deepalgorithm|LINK
WCF is generally used for SOAP and Web API for REST. RESTful services like Web API are simple and light weight and easy to access by any client which supports HTTP calls. WCF is a heavy framework and requires a lot of configuration. A WCF client
needs to understand WSDL to implement the service.
It seems you are building a line of business application with CRUD operations (create, read, update, and delete). Bottom line, if performance and quick development cycles are your criteria, WEB API is probably a better choice.
That being said, it's worth reading this MS doc.
Jul 21, 2017 07:51 PM|codemovement.pk|LINK
It is based on SOAP and return data in XML form.
It support only HTTP protocol.
It is not open source but can be consumed by any client that understands xml.
It can be hosted only on IIS.
It is also based on SOAP and return data in XML form.
It is the evolution of the web service(ASMX) and support various protocols like TCP, HTTP, HTTPS, Named Pipes, MSMQ.
The main issue with WCF is, its tedious and extensive configuration.
It can be hosted with in the applicaion or on IIS or using window service.
To use WCF as WCF Rest service you have to enable webHttpBindings.
It support HTTP GET and POST verbs by [WebGet] and [WebInvoke] attributes respectively.
To enable other HTTP verbs you have to do some configuration in IIS to accept request of that particular verb on .svc files
Passing data through parameters using a WebGet needs configuration. The UriTemplate must be specified
It support XML, JSON and ATOM data format.
This is the new framework for building HTTP services with easy and simple way.
Web API is open source an ideal platform for building REST-ful services over the .NET Framework.
Unlike WCF Rest service, it use the full featues of HTTP (like URIs, request/response headers, caching, versioning, various content formats)
It also supports the MVC features such as routing, controllers, action results, filter, model binders, IOC container or dependency injection, unit testing that makes it more simple and robust.
It can be hosted with in the application or on IIS.
It is light weight architecture and good for devices which have limited bandwidth like smart phones.
Responses are formatted by Web API’s MediaTypeFormatter into JSON, XML or whatever format you want to add as a MediaTypeFormatter.
Choose WCF when you want to create a service that should support special scenarios such as one way messaging, message queues, duplex communication etc.
Choose WCF when you want to create a service that can use fast transport channels when available, such as TCP, Named Pipes, or maybe even UDP (in WCF 4.5), and you also want to support HTTP when all other transport channels are unavailable.
Choose Web API when you want to create a resource-oriented services over HTTP that can use the full features of HTTP (like URIs, request/response headers, caching, versioning, various content formats).
Choose Web API when you want to expose your service to a broad range of clients including browsers, mobiles, iphone and tablets.
Jul 24, 2017 01:59 PM|PatriceSc|LINK
Favor web api over WCF (ie use the simplest option that works). Not sure though to see how it helps to reduce the db load. Make sure to solve an actual problem. To me writing short values to a write only table shouldn't be where your app will suffer most.
Depending on what you want to track exactly you could also see if the IIS log couldn't be enough.