Thread: Pros and cons of using an external MySQL database?

Some issues you will face, although it is done frequently:

1. There will be a latency issue but depending on the data it may not be noticeable
2. MySQL connections tend to be clear text by default - so you need to take care. Just sending people's e-mail addresses for example, are stricly governed
3. Errors/Speed - try to keep it stateless (i.e. don't expect you have connection, be prepared to open it with each query)
4. HTTPS is between the web host and the client user (Browser <-> web server). You won't be connecting on HTTP/HTTPS protocols generally speaking, to the MySQL Server

Settings like whether or not you can use SSL data transfer, which IP's may access it are down to the admin and not generally open to modification on shared hosting platforms.

I think link8r covered it but I just want to re-iterate, that you should be wary about the type of data your transmitting over open 'space'. If its personal data like names, DOB, emails, address, or even a payment process you will need to have sufficient security in place like SSL to protect this data as you don't want to be open to legal action should people's personal data get into the wrong hands.

Hi,

One option I recommend you to consider is to have your database provided as a service.

You can check out our blog post on the pros and cons of deploying it yourself vs. having DBaaS.

Move Your MySQL Database to the Cloud: DYI or Database Service? | Xeround MySQL Cloud Database Blog