Very fast database Web API

Instant database Web API? The biggest advantage of a Restful API is that you don’t have to install anything on the client side (i.e. Your app for example). No SDKs or frameworks are needed nor required. All you have to do is to make a simple HTTP request to the target API service, let the server do the precessing for you and get the result back. Suppose for example, you wanna build a Snapchat clone app. You need for that an image/video processing library, an augmented reality toolkit and an SDK for facial feature extraction. As you may notice, this is time consuming and require a lot of work integrating all the complex libraries into you program.

Benefits of REST Over SOAP. In addition to using HTTP for simplicity, REST offers a number of other benefits over SOAP: REST allows a greater variety of data formats, whereas SOAP only allows XML. Coupled with JSON (which typically works better with data and offers faster parsing), REST is generally considered easier to work with.

Use Subresources to Show Relationships: An attractive alternative to only using top-level resources is to use subresources to make the relationships between resources more obvious to the API user, and to reduce dependencies on keys inside the resource representation. So how do you decide what resources should be subresources? A rule of thumb is that if the resource is a part of another resource then it should be a subresource (i.e. composition). For example, if you have a customer, an order and an order line then an order line is a part of an order, but an order is not a part of a customer (i.e. the two exists independently and a customer is not made up of orders!) The idea with subresource is to make your API more readable. For example, even if you don’t know the API you can quickly guess that POST /customer/123/orders will create a new order for customer 123. However, if you end up with more than about two levels then the URI starts to become really long and the readability is reduced.

Use Visual Studio 2017 to create an empty Web API project. Make sure you add unit tests to the solution. This empty solution will be used as a stub for the generated code. Step 2 Run InstantWebAPI application, select the stub Visual Studio solution file (.sln) created in first step. Using a database connection dialog create a connection string to your server. Application supports MS SQL server, Express or Azure. Once a connection is established to the database, select the tables or views for which Web API needs to created and start the code generator. Read more details on Create ASP.Net Web API from MS SQL in Minutes With Instant Web API.