MySQL leverages application architecture and works well.
September 29, 2016

MySQL leverages application architecture and works well.

Anonymous | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with MySQL

We use MySQL database as part of the integrated migration solution on the apps servers as part of migrating customer data from one billing solution to another billing solution. It is used in the client project on a customer side as part of an uprising migration framework. They were integrated with an Oracle Database at the backend to seamlessly ingest data and process and migrate millions of customers to the new transactional databases.
  • MySQL is open source and can be easily integrated in the application layer without much hassle of managing a large relational database.
  • MySQL performs well in the larger workload and provides multiple configurations for clustering and scalability.
  • Monitoring capability for MySQL instances and ability to integrate in one centralized console like Netcool.
  • Migrate MySQL database to Oracle - there may be room for improvement.
  • Migrate Oracle Database to MySQL database - they may be room for improvement.
  • MySQL License are cheaper compared to other RDBMS licenses and generate good ROI when properly used for the business.

I've used both Oracle and MySQL. I like both database technologies. Both of them provide great solutions. Each one has their own benefits based on the requirement and right environment. The point is to find the right environment to use and compare price/performance/scalability.

  • MySQL is relatively light-weight, can be extremely fast when using applications architecture. They have lots of features such as clustering, replication and partitioning.
  • Oracle offers lots of features/functionality for solving complex problems. Supports large OLTP environments as well as VLDBs in terabyte or even petabyte scale.
From my experience, MySQL is suited well for a database that can be easily embedded in the application layer and also for databases that are read-only replicas. They are not well suited for an application that runs or requires complex queries with multiple table joins and explain plans. They are not very robust compared to an Oracle Cost Based optimizer.