Immediate Rest API from your MS SQL database? 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.
Another advantage of SOAP is that it offers built-in retry logic to compensate for failed communications. REST, on the other hand, doesn’t have a built-in messaging system. If a communication fails, the client has to deal with it by retrying. There’s also no standard set of rules for REST. This means that both parties (the service and the consumer) need to understand both content and context. At the end of the day, the best protocol is the one that makes the most sense for the organization, the types of clients that you need to support, and what you need in terms of flexibility.
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.
When I ran InstantWebAPI I get an error message about writing rights. How can this be fixed? If you created the stub solution as an administrator, then InstantWebAPI needs to be run as an administrator as well. We have a database with 80 tables. How many tables and views can this software generate the code for? This code was tested against databases with more than 100 tables. Web API project code gets generated pretty fast, but generating Unit Test code it might take a while. We recommend generating the code for a limited number of tables at a time. We have a database with multiple schema. Can the code be generated for all the schemas at the same time? No, this version of the software only allows generating the code for one schema at a time. Further customization can be added by sending a requests to Customer Service. Find extra details at Use Core EF to build Instant Web API.