Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

So I’ve started using the managed databases, granted I impulsively did it, not for leaving MySQL intentionally, I would have stayed if that launched first, but because of a reliable cluster.
But anyways. Is there a special case as to why we’re only using a domain to access our cluster instead of IP? Such as routing behind the address due to it being a cluster, or simply out of proxying and security?
As I transitioned over I only noticed an additional 2ms-5ms in latency vs using a local database through socket, which is not bad at all, but I wonder if directly connecting through a private IP would be beneficial over the domain, because currently, I don’t know if we’re routing directly to the management database in the same datacenter or not.
Anyways, thanks for taking the time to look over the question, it’s been on my mind for the past week.
jeffs
0621335d663b4b699a60eb27e28153
accesstrax
Dwight Trumbower
admin
yimprogramming
samunyi90
1d6ce141ab5444dfb1ea2dd29cf4b1
Matt Fricker
joel9b158e40551b15093f213f
EmilJacobs