Immediate database Web API

Build and deploy your REST Web API in no time, no code required? 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.

SOAP (Simple Object Access Protocol) and REST (Representational State Transfer) are both web service communication protocols. SOAP was long the standard approach to web service interfaces, although it’s been dominated by REST in recent years, with REST now representing more than 70% of public APIs according to Stormpath. Understand the primary differences between SOAP vs. REST and how each can benefit your organization’s goals.

The promise is that if you wait with thinking about shared data until you know what business capabilities you need to offer, it will lead to a less database-oriented design. I think his approach is a good way to jolt you out of the database-driven mindset, but you need to be careful that you don’t end up designing a REST-RPC hybrid. What I also like about this approach is that it minimizes the interface and doesn’t expose all data by default, but hides internal data (like logging and configuration tables) from the client and instead focuses on what the client actually needs. This also fits beautifully with veteran API designer Joshua Bloch’s maxim saying that When in doubt, leave it out (from his highly popular presentation on API design), and it also harmonizes with the REST principle that a representation of a resource doesn’t need to look like the underlying resource, but can be changed to make it easier for the client. So feel free to think about what would be the easiest interface for the API user, and then let your resource take data from multiple tables and leave out columns that are irrelevant to the job that clients need to perform.

Code will be generated into the initial stub Visual Studio solution. At this point the solution can be build and is ready to use. The solution should contain 2 projects; one for the actual Web API and another one for Unit Tests. Using the Unit Test project you can test the quality of the Web API that was generated. The Web API project should contain a referrence to Swagger UI, that allows for clear documentation and testing of the newly created API. Build an instant database Web API now, no coding required. Generate your Web API in minutes to build applications faster. Using Entity Framework 6.2.0 and VS 2017 generate your Web API for any MS SQL database. NEW – Use Core EF to build Instant Web API! Using Core Entity Framework 2.2 and VS 2019 generate your Web API for any MS SQL database. Discover extra info at Use Core EF to build Instant Web API.