Few clicks Rest API from your MS SQL data source

Build and deploy your REST Web API in minutes, no code required? A well designed API is self-documenting. If you know how to work with one REST API, you will quickly learn the quirks of others. InstantWebApi is an API-first product. I spent a lot of time on API design. My intent is to be able to hire multiple teams in parallel, giving them access to my API, and seeing which implementation I like best. They will all be compatible. I can then simply discontinue the less interesting implementation projects.

Thanks to JSON, REST offers better support for browser clients. REST provides superior performance, particularly through caching for information that’s not altered and not dynamic. REST is the protocol used most often for major services such as Yahoo, Ebay, Amazon, and even Google. REST is generally faster and uses less bandwidth. It’s also easier to integrate with existing websites with no need to refactor site infrastructure. This enables developers to work faster rather than spend time rewriting a site from scratch. Instead, they can simply add additional functionality.

You also need to be aware that subresources cannot be used outside the scope of their parent resource. In the second example, you need a customer id before you can lookup a order, so if you want a list of all open orders (regardless of customer) then you cannot do it in the second example. Ehh, so what to pick? If you want a flexible API, aim for fewer subresources. If you want a more readable API, aim for more subresources. The important thing is that whatever rule of thumb you pick then be consistent about it. I mean the API user might disagree with your decision, but if you are using it consistently throughout your API, he or she will probably forgive you.

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. See more info at Instant database Web API.