Why you should avoid to directly connect your mobile apps to a remote database?

In Mobile Development by Christian HissibiniLeave a Comment

You may be wondering why you couldn’t just connect directly to a database from your mobile app? The main reasons are:


You don’t want your mobile client apps to have a database connection string with a username and password in it. It opens your database up to anyone. You can create a user with read only permissions and only allow access to certain tables, but they could still see all data in these tables. On an API, you can implement additional security checks and have authentication based on OAuth or an existing user management system.


Database connections weren’t designed to go over high latency connections. It is likely your database connection would keep dropping, forcing you to reconnect every time.


With an API you can control the flow of data to and from your database. You can implement rate limiting, and monitoring of all of your requests. If you need to change business logic, or even what database or resources are used via each API request, you can do this on the server, without having to redeploy a mobile app.


With an API, you reduce the need for server resources. While you may have to setup another server to handle an API, the REST API is designed to be stateless and efficient. Scaling to many users in the future is easier with an API.

https://docs.microsoft.com – https://xamarinhelp.com – https://blog.xamarin.com/

Leave a Comment