When it comes to Data Access performance of .NET application, many people focus on the tuning and optimizing the Backend datasources. But there is lot to gain from just tuning your connectivity solutions for the need of your application.
This presentation focuses on how to tune your ADO.NET connectivity solution to get the best performance out of them.
In my job as an Evangelist, i speak to numerous customers of ours. Many a times the customer is in an evaluation mode. They are trying out our tools and have plenty of questions on their mind. My job is to talk to them, understand their problem and provide a solution. I must say I love this exercise, as i get to hear a new problem with every new customer we talk to. Figuring out a solution to a challenge is always a happy moment. Today we discuss one such problem that a customer was facing with respect to Hybrid Mobile Apps.
On Sep 4 2014 we conducted a webinar titled “Connecting your In-Premise Database to Mobile Apps”. This was part of regular webinars we conduct almost every Thursday of every month for India time zone. This post is a recap of the webinar.
One of the pressing issues enterprises often face when it comes to mobility is how to connect to an in-premise database from a mobile application. Scenario is that the enterprise does not want to move the data outside of the organization i.e. move to a cloud infrastructure. Rather they want to keep the data inside the organization but still be able to access it from a mobile application. In this webinar we look at 2 solutions/techniques to solve this problem. They are:
Use ASP.NET WebAPI to create a service and host it inside the organization, expose it as a public IP behind fire wall and consume from a mobile app
Use Telerik BackEnd and in particular DataLink & DataConnector to expose data as a RESTful service without writing any code
Below you will find the slide deck used for the webinar, video recording of the webinar, Q&A and T-Shirt winners.
Q & A:
Q: HOw Does webAPI serve when more request (traffic)?
A: The web server can be used to manage the web traffic. You can also create web farms if you expect more traffic.
Q: How rLinq is different from edmx?
A: It is almost the same. EF (edmx) can be used here as well. rlinq also has L2 caching support that helps speed up the application.