Turn off updating intellisense
In the past few months we've seen a few questions about using Kendo UI with Microsoft's ASP. The gorilla in the room is "Does Kendo UI Work With Web API? The most commonly used of these for creating RESTful services is probably ASP. Just when we were all becoming comfortable with MVC, Web API showed up. NET MVC, and Web API to identify some of the differences between the two. One is to use straight Kendo UI Java Script, and the other is of course to use the MVC Server Wrappers. It is agnostic of what your server is doing and in the end, really just wants you to provide it with a healthy diet of JSON data. You have a cornucopia of options when it comes to using ASP. Essentially, you can get your data as JSON using any of the following: All of those are capable of returning JSON data via a URL, which is precisely what you want when building HTML5 applications.Developers were previously faced with two options: either over-provision database resources based on peak usage--and overpay.Or under-provision to save cost--at the expense of performance and customer satisfaction during peaks.
You can parse the parameters out of the Request object, or you can create your own custom Data Source Request class and let MVC Parameter Binding take over.
Kendo UI itself is engineered towards open web standards and does not cater to a specific technology stack. NET as Scott Hanselman is fond of saying, but that doesn’t change the fact that all the choices, acronyms and technologies can get really confusing.
Web API allows you to more easily adhere to a RESTful schema with your URL’s and is very closely related to ASP. You have several options comes to using it with each of these with Kendo UI. If you decide to use the Kendo UI Java Script libraries directly, returning JSON is simple. NET can serialize your response, this is all there is to it.
This has the benefit of isolating the data for each customer separately (and enables each customer’s data to be encrypted separately, backed-up separately, etc).
While this pattern is great from an isolation and security perspective, each database can end up having varying and unpredictable resource consumption (CPU/IO/Memory patterns), and because the peaks and valleys for each customer might be difficult to predict, it is hard to know how much resources to provision.