Amazon Aurora

Best RDS Solution

Kommentare: If you are looking for a best solution in cloud or hybrid environment, go for it.

Vorteile:

Amazon Aurora is a wonderful Relational Database Solution in the AWS Cloud, it can provide you with up to 15 read replicas, it is amazingly server-less. You don't need to worry of capacity and performance.

Nachteile:

It is a bit expensive as to the other available solutions, but considering its features it is a good choice.

No concerns for speed or our SLAs

Kommentare: Years ago, as our product and userbase grew enough that basic RDS wasn't cutting it, our IT team was surprised at how affordable the move to Aurora was, considering all the improvements. We've never looked back and don't have to spend nearly any working hours on scaling, migrations, and backups. We couldn't do what we do with out it.

Vorteile:

The reliability, speed, and ease of scaling that Aurora offers are unmatched at their price. RDS was great when we started out, but with our software's growth, moving to Aurora was an easy decision.

Nachteile:

The software has pretty much checked every box we have for managed database solutions. The only *ding* they get is for some often slow support response times/solutions.

MAke Services Esier

Vorteile:

everything on one platform thats the most amazing things.

Nachteile:

Hard functionality. find out other option is hard

Aurora - if you're on RDS, you should definitely give it a look

Kommentare: We had been on RDS for a number of years, happily running mySQL, when Aurora came out. The timing felt good: Oracle was just about buy mySQL (I think - not 100% sure on timing), so we were already feeling a bit edgy about what future support for mySQL was going to cost. It was hyped as a cheaper, faster alternative to mySQL -- and once we dipped our toes in the water, we discovered that's pretty much exactly what it is. We run a number of enterprise-class websites on an RDBMS backend, and we migrated from mySQL to Aurora within a few weeks. It was as simple as running database dumps, importing them into Aurora, and changing the pointers. Really. The interfaces are all identical, we didn't have to change any code at all (except for one thing -- see below), and once we cut over, it just worked. Which is basically what you want from your database. I'm very happy we switched over, and honestly, I still just kind of think of our database as mySQL. I use mySQL GUI tools to connect to it, write regular mySQL SQL queries to interact with it, and everything else just feels like the mySQL I grew up with. Only it's significantly cheaper, and feels faster. Win. The only caveat: there was one plugin we had in our mySQL install (it was a thing that let you do Levenshtein distance calculations) that was incompatible with Aurora. The plugin didn't exist. If you have a SUPER customized mySQL setup, look into whether Aurora supports all you do. But for us we never looked back.

Vorteile:

* Pretty much a one-for-one swap with mySQL, only faster and cheaper * Not any learning curve * Super reliable

Nachteile:

* If you have a seriously customized mysql installation, there may be some plugins that don't work

AWS Aurora A must have RDBMS

Vorteile:

Ease of configuration and usability. From the beginning I found it easy to use and handy

Nachteile:

at integration level ,I think we can work to make it more seamless