MySQL Router  /  Deploying MySQL Router

Chapter 3 Deploying MySQL Router

Performance Recommendations

For best performance, MySQL Router is typically installed on the same host as the application that uses it. Possible reasons include:

  • To allow local UNIX domain socket connections to the application, instead of TCP/IP.

    Note

    Unix domain sockets can function with applications connecting to MySQL Router, but not for MySQL Router connecting to a MySQL Server.

  • To decrease network latency.

  • To allow MySQL Router to connect to MySQL without requiring extra accounts for the Router's host, for MySQL accounts that are created specifically for application hosts, such as myapp@198.51.100.45 instead of a value like myapp@%.

  • Typically application servers are easiest to scale.

You can run several instances of MySQL Router on your network, and do not need to isolate the router to a single machine or even a single Router instance. This is because MySQL Router has no affinity for any particular server or host.

Figure 3.1 Example MySQL Router Deployment

The figure content is described in the surrounding text.


User Comments
Sign Up Login You must be logged in to post a comment.