Yes, and then setup keepalived on them so you have a stable VIP that is guaranteed to move between them. I did a writeup of how we did it (when I worked there) for ticketmaster here:
The gist is that you have a dummy interface ie: dummy0, and when you down that interface, the VIP flips to the backup node with the highest VRRP priority.
> Guess it's best to setup Master to Master replication..
Master-Master has issues of its own, if you use shoddy applications that assume next-id=max(id)+1.
In the worst case situation you can find data on one master, and not the other, and vice-versa. So be prepared to reconcile things if you get into a split-brain scenario.
I do agree, We do setup for HA, but due to some bugs on our end, the cut over from our DB Slave to Master didn't happen. Will be more careful next time.
Thanks again for providing all of the detailed comments concerning the advanced notifications for pricing changes. Your points are sound, and I understand that especially for customers with high volume use cases, relying on the pricing CSV file would not remove the costs of sudden price changes and would pose an the obstacle to the pro-active re-routing of traffic.
I've shared all of your comments with our product team, and I'll let you know as soon as I have more information concerning potential pricing change notifications. This would be a major change in the way that we price our Global SMS service, but I hope to be able to pass along some comments from our team by the beginning of next week.
We appreciate your thoughts about our SMS service and our pricing. I'll provide an update as soon as I can."
Thanks everyone for the suggestion..this is followup question, both
I am bad at finding a good domain name for my product and service, since secureme.com is taken, what is the next best name for my product..
