I've looked at Xeround - not sure how cost effective they are. For a decent sized database (30GB+) their calculator shows it to be over $2000/mo.
I'm really intrigued by Amazon RDS - you're basically just paying for an instance (which for decent performance is quite cost effective). You can get a read-only replica, or a hot-swap replica. As I understand it, if you use a hot-swap replica, it'll have the same DNS/IP info, so relatively transparent as far as JDBC goes. (May not scale as well as Xeround, I don't know) Billy Cravens [email protected] On Jan 3, 2012, at 9:53 AM, Alex Skinner wrote: > Check out http://xeround.com/ > > I've been trying this its replicated Active / Acrive MySQL in the > cloud > > I've not managed to get the JDBC failover stuff working yet but I > think thats a bug im just testing from Java to confirm > > A > > On Jan 3, 3:32 pm, Jason Allen <[email protected]> wrote: >> Hi Guys, >> >> I'm trying to make a decision on whether I'm going to stay with >> Microsoft SQL, or move to mySQL. >> >> I'm building an app, and while it has many tables and databases, the >> tables themselves aren't anything special and so far I haven't seen >> any reason I couldn't port them to mySQL very easily. I'm not locked >> into any stored procedures or anything. My app's SQL language is very >> straight forward and nothing too complicated. I'm sure I'll have to >> rewrite some of the queries but they all work as is so it shouldn't be >> hard to make the switch. >> >> My issue is really cost. I want to setup the app so that the database >> has redundancy and replication. I can launch on SQL Express to start, >> since it's free, but that doesn't offer anything in the ways of >> replication, etc. Once I get into some serious real time replication >> and clustering, I need SQL Enterprise, and it's very expensive for a >> single CPU license. >> >> With mySQL, I'm not bound by licensing costs, and the 'free' version >> comes with replication out of the box. A coworker of mine is very >> experienced with managing mySQL, including setting up clusters, >> replication, etc. and he's willing to help me get it all setup. >> >> My thoughts are, if I get the mySQL cluster setup right from the >> beginning, I'm launching with a much better infrastructure and >> disaster recovery plan. It would cost me thousands of dollars in >> licensing to get this same setup with MS-SQL, and that would just be >> for single CPU licensing. If I saw any kind of growth, especially if >> it was fast, the licensing costs could soar above $100,000 quickly. >> I'd rather spend that money on hardware and paying an admin to help me >> manage a mySQL cluster. >> >> Since I'm using OpenBD, I'm asking this community on their thoughts. >> Is there any glaring reason NOT to move to mySQL? I'm personally much >> more versed with Microsoft SQL (certified) but it seems like a better >> investment to move to mySQL. >> >> Thanks! > > -- > online documentation: http://openbd.org/manual/ > google+ hints/tips: https://plus.google.com/115990347459711259462 > http://groups.google.com/group/openbd?hl=en > > Join us @ http://www.OpenCFsummit.org/ Dallas, Feb 2012 -- online documentation: http://openbd.org/manual/ google+ hints/tips: https://plus.google.com/115990347459711259462 http://groups.google.com/group/openbd?hl=en Join us @ http://www.OpenCFsummit.org/ Dallas, Feb 2012
