Amazon Aurora vs Azure SQL Database

• Aurora is a relational database as a service on AWS which is MySQL and Postgres compatible. So if you are looking for a serverless option which going through need to host and manage a database then Aurora as a service is great.
• It is a simple and cost-effective open source database which is much cheaper than a normal database cost. Hence very efficient for microservices database where you do not need one very large centralized database but many small databases that are available and low latency.
• Aurora provides high performance and low latency. Last year they also announced multi-master in the same region and read replicas in multiple regions. This is very convenient if you are trying to design and build a highly reliable application.

Read full review

• No more internal servers is a big plus.
• Transition was relatively easy since we came from another Microsoft database before.
• Query running time has significantly improved

Read full review

• The cost of Amazon Aurora when compared to a simple MySQL instance is considerably higher, so we really need to look at and run some performance tests to compare if the performance improvements are worth the extra cost.
• Although backup restores are a rare feature to use, when we need them it is always painful to restore our data. We are always searching for a database service to provide new and innovating features in terms of data recovery. For instance, being able to search on backup information to see if the needed data is there. It is a very common need to compare the hot data with the backup data, for example to fix some database data that a malfunction application wrongly updated.
• Since aurora is an Amazon relational database service there is no way to run a dev database on a local storage for tests and development.

Read full review

• Intelligent recommendations are not a silver bullet, since they often fail to detect opportunities that are obvious to a human database admin with any experience.
• Certain advanced database features - most recently I found: column store indices - are locked behind pricing tiers that one would naively assume are just about performance.

Read full review

• The main positive for my team is the time that has been freed up from the tasks of managing updates and fixing replication issues.
• A negative for myself as a database administrator is removal of features that were available in Mysql. Examples include 1) the use of the storage engines other than InnoDB (such as the Federated Storage Engine), 2) certain administrative privileges such as ability to export to csv file and easy ability to kill processes. I seem to also forget they removed the built-in kill ability and you must use their own provided kill functionality.

Read full review

• As compared to On Site SQL server AZURE is less hectic and less responsibility to worry for.
• It pretty much easy to follow devOps or Agile for Backlogs as AZURE allows to take care of its own things.
• Database scalability, Patching and Upgrading is the best thing it gives in return

Read full review