MySQL Reviews

We are developers working on different types of projects. We use relational databases in some projects and non-relational databases in others. When we use relational databases, we use MySQL. When we use non-relational databases, we use our DynamoDB or MongoDB.

1. Ease of Use: MySQL is relatively easy to set up, configure, and manage, especially with tools like MySQL Workbench and command-line utilities. Its widespread popularity also means there is ample documentation, tutorials, and community support available for users.
2. Open Source and Cost-effective: MySQL is open-source software, which means it is free to use and can be customized according to specific requirements. This makes it a cost-effective choice for startups, small businesses, and projects with budget constraints.

Compared to some other database systems, MySQL may have limitations in terms of advanced features and functionalities, especially when it comes to complex data relationships and transactions.

I have been using MySQL for two years.

In my past two years of MySQL experience, I found no bugs or breakdowns. It works completely fine.

Many cloud providers offers managed mysql service with scalable architecture ,automated backups , monitoring and scaling. Leveraging this can solve the scalability problem.

MySQL is very easy to install and use.

As it is an open source and there is community edition available so if you have small or medium use case it is much cheaper to use.

Below are some thing to consider while working with mysql.

1. Regular maintenance 

2. Security consideration

3. Version compatibility

You can try MySQL if you have any use cases of relational databases. It is very easy for somebody to learn to use MySQL for the first time. The solution worked fine for me, with no breakdowns or scalability issues.

Overall, I rate MySQL eight and a half or nine out of ten.

We use it to meet the requirements of our customers while optimizing performance and reliability within the constraints provided.

The performance and scalability of our project have been influenced positively by MySQL. From what I've observed, performance has been satisfactory, and I haven't received any complaints from teams that have implemented it.

While MySQL offers strong basic functionality.

MySQL lacks a feature akin to Oracle's Real Application Clusters, which ensures continuous database availability within the same data center or nearby data centers. Without this capability, MySQL's suitability for mission-critical applications is diminished. Until MySQL incorporates a similar feature at the application level, its appeal for high availability remains limited. Historically, we've relied on external security measures for data protection, such as encryption. However, when encryption methodologies are employed within MySQL, there may be a slight performance degradation due to the computational overhead associated with processing large volumes of data in the database.

I have been working with it for twelve years.

Stability is crucial, and it's influenced not just by the inherent features of the database system, but also by how the application team writes queries. If queries are poorly written or not optimized, it can affect stability significantly. While logging can help, improper usage, such as logging entire tables instead of specific fields, can also impact stability. Therefore, ensuring stability requires a holistic approach that considers both the database infrastructure and how the application interacts with it.

Scalability is not as straightforward with MySQL compared to Oracle. I would rate it seven out of ten. Our clientele typically includes small, medium, and enterprise-level businesses.

The initial setup was straightforward. I would rate it nine out of ten.

For the MySQL installation, it's crucial to have a broader understanding of the solution we're implementing. Sometimes, we may need to address OS-level issues, especially when dealing with OS-level addressing like OSFlow. In such cases, thorough testing at the voice level is essential to ensure a smooth installation process. Implementing MySQL in a single-node setup may uncover additional challenges that need to be addressed.

Typically, our focus is on implementing the product rather than the database or operating system level. While I oversee infrastructure aspects, the implementation process is heavily influenced by the specific application being deployed. From setting up voice-level deployment and alerting to handling licensing and the database infrastructure, this entire process usually takes four to six weeks, depending on the complexity of the functionality. Once we complete the initial deployment, subsequent enrollments become more streamlined, and the application is handed over for production use. Any further adjustments or configurations are managed separately.

The pricing falls within the moderate range. I would rate it four out of ten.

Rather than recommending specific servers or operating systems, decisions are driven by how the application behaves and what functionalities it requires. This approach streamlines the process as pre-tested systems are already available, reducing the time and investment required for testing. Overall, I would rate it eight out of ten.

I use MySQL as a metadata database to store information about our product and transactions from other platforms. We extract and store these transactions daily.

I find MySQL's relational data storage format very useful for data management. Our structure is well-defined and easy for end users and business stakeholders to read. I appreciate the tool's simplicity and ability to integrate with our backend tools.

Performance optimization techniques in MySQL are foundational and very useful. Many big database tools are based on their techniques. We use basic optimization methods like indexes and constraints, which should be set up early when designing the database schema. These optimizations are important for us and work well with MySQL.

As for areas that could be improved, the tool is often used as a local database on laptops. But now, we're moving to cloud-based solutions that are more scalable and highly available. I think the tool should offer a cloud database option. This would let users keep a local copy of data if needed, but also have their data available across different regions through a cloud account. 

The product's stability is high. 

I rate the tool's scalability as about six out of ten. It's moderate since it's a relational database, so scalability depends on the data volume we can store. We use MySQL mainly for structured data in its final state. About 1800 people use MySQL in our organization. Around 1200 use it daily, and about 600 developers use it for local databases or small project tasks.

MySQL has been in the market for a long time, and its community keeps growing. As developers, we've gotten full support from them since we started using it. This includes help from their support team and software team and assistance with any technical issues we encounter.

Positive

I'd rate the initial setup as nine out of ten for ease, with ten being the easiest. It's very simple for beginners to set up because the documentation is thorough, and each step is well explained. The deployment usually takes minutes to hours, depending on the data volume we're putting into the database. It typically doesn't take longer than a day.

MySQL has had a moderate impact on our cost efficiency so far. We mainly use it for local development in our internal environments. For production, we use other cloud solutions. However, MySQL's impact on our operational productivity is significant. It's very reliable for all the solutions we're building.

I rate the solution's pricing as four out of ten, where one is cheap, and ten is expensive. For our basic needs, it's quite affordable. However, the cost increases when we need to scale up or require high availability. Our developer team of about 600 people uses MySQL without much issue. The pricing becomes more of a concern on the business side, as we have more end users and need constant database availability and scaling. In those cases, the solution gets a bit more expensive, even though it provides good value for the business.

I rate the overall solution a nine out of ten. 

MySQL was open-source at the beginning until Oracle acquired it in 2010. I started working with MySQL because I was an Oracle expert, having worked for Oracle for eight years. That's why I added MySQL to my skills as an administrator. MySQL is a powerful database engine that is easy to install, manage, and work with. It's ideal for fast application deployment and is cost-effective as well.

MySQL is for metadata and data. My organization has used it to store data about hardware servers and their configurations, including network and storage configurations. MySQL is an RDBMS engine, so it can be used for any business application.

MySQL has a straightforward installation process, is lightweight, and easy to manage. Compared to its competitors, it is more accessible and user-friendly. While competitors like Oracle are known for their extensive features, they are often more complex to install, configure, and maintain, requiring experts to manage them, which can be costly. MySQL, now owned by Oracle, may not have the same feature set as Oracle's flagship database, but it is simple to install, manage, and cost-effective. MySQL is a viable option that can be enhanced with additional features, making it reliable for small to medium-scale applications and capable of effectively handling substantial amounts of data.

MySQL is now in a real application cluster. In terms of high availability, MySQL can be configured for active-active or as a real application cluster.

I have been using MySQL for ten years.

When MySQL is involved in the metadata, it never gets down. It's very stable.

It's secure. MySQL supports large databases that can contain nearly fifty million records. It also supports up to sixty-four indexes per table.

They provide 24/7 support. It provides faster resolution and identification.

Positive

It is very easy to install and takes an hour to complete.

I rate the initial setup a ten out of ten, where one is difficult and ten is easy.

It is open-source and supported by Oracle.

Oracle occupies it, so Oracle added more security features, such as password system improvements, host-based verification, and encryption, to the MySQL engine. It's developed and managed by a big company, and they keep adding new features.

I recommend another solution for large data, like billions of records. However, MySQL is a good option for data up to about fifty million records.

Overall, I rate the solution an eight out of ten.

MySQL is an open-source relational database management system used to store data.

MySQL is an easy-to-use solution that provides stability, reliability, flexibility, performance, security, and high availability.

MySQL could introduce more indexing strategies. There are a couple of strategies where you can index things to be more searchable and visible. We lack that kind of functionality. For example, if your name is indexed correctly with a certain strategy, it can improve the search results faster. The solution’s interface could be improved.

I have been using MySQL for my entire career.

MySQL is a stable solution.

MySQL is a scalable solution.

The solution’s initial setup is easy.

MySQL is a free and open-source solution.

MySQL is deployed on the cloud in our organization. Big companies like Netflix, Uber, and Facebook use the solution. Since MySQL is an old product, many people might have faced similar issues, posted them online, and got a resolution. MySQL's performance and scalability features have supported our database growth.

New users can follow the documentation to use the solution, as it is straightforward. You need to be very clear about why you want to use the solution. MySQL is a relational database management system that cannot be used as a dynamic database management system.

MySQL is generally faster and more efficient than other relational database management systems. Hence, it is our preferred choice for applications that require high performance.

Overall, I rate the solution a nine out of ten.

Our primary use case for MySQL is for our internally-built system. When our developers are doing the assistance, usually we provision them with the MySQL driver.

The way that MySQL has improved my organization is that it comes free and also works fine on the technical side.

The feature I found most valuable was the cluster setup.

The integration with other systems can be improved as can the integration between other databases. We have a workaround to integrate it with other systems but that can be improved.

In the next release, I would like to see better day-to-day support in case we face any issues.

I have been using MySQL since 2008.

I would rate the stability of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best. We have a team of three DBAs supporting and maintaining this product.

I would rate the scalability of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best. I believe MySQL very scalable.

I would rate the technical support an eight, on a scale from one to 10, with one being the worst and 10 being the best.

Positive

I would rate the initial setup process a nine, on a scale from one to 10, with one being the worst and 10 being the best. I would say that this process has been quite easy.

The deployment of this solution was done by an in-house team and it took around 30 minutes to one hour.

I would rate the pricing of this solution a two, on a scale from one to 10, with one being not expensive and 10 being very expensive.

I would recommend this solution to other people.

Overall, I would rate MySQL solution a nine, on a scale from one to 10, with one being the worst and 10 being the best.

We use MySQL in multiple projects for storing, task management apps, and dating apps.

MySQL is the best option for the Laravel PHP framework. It supports multiple model systems, and it's very easy to call MySQL compared to other languages like MongoDB. I prefer MySQL for the Laravel PHP framework.

The solution's security features depend on where we host our server and database. We have some preventive measures to reduce attacks. We have taken authentication and only allow a particular IP address.

In MySQL, we need to define every table beforehand.

I have been using MySQL for four to five years.

In MySQL, we need to define every table beforehand. However, we don't need to do so in MongoDB. We can add a new row or column in MongoDB anytime, making it much easier. If you purchase MongoDB's plan, it supports many security features, and you don't need to check about security. They will handle everything.

The solution’s initial setup is very easy. For the first time, the solution's implementation will take some time. However, you can use it multiple times after you configure it.

MySQL is a cheap solution.

Maintaining the database is a task. We take a weekly backup for each database so that we can upload it to the server if anything happens to the data. We created a cron job so that the data can be taken and then uploaded to a specific space so that we can go back to the particular big data whenever we want. I prefer MongoDB for scalability because it's much easier to maintain MongoDB.

Just one person is enough to maintain the solution. The solution has good documentation available on Google.

Overall, I rate the solution six and a half out of ten.

I use the solution for personal use cases like software development, mostly database bug systems.

I used the tool to build our website. It is used as a database to store information.

SKIP LOCKED is a valuable feature. It prevents us from deleting things we put in the database. It's mostly for background jobs in the software development site in MySQL 8. It is a new feature. The solution easily integrates with other tools and systems in our IT environment.

The full-text search feature must be improved.

I have been using the solution for the past three weeks.

I rate the tool’s stability an eight out of ten. We can create a database user schema. It's quite easy to update and remove in case anything happens. Backing up is quite easy. We have security features for the backup.

I’m the only user in my organization.

The product provides good documentation online.

It is easy to deploy the product. I deployed it on my own. The deployment took an hour. We deploy the product using Kamal. It uses Docker. The tool is deployed on the cloud. To deploy the solution, we just have to enter the password in the server and deploy it. It wasn't much of a hassle.

The tool is easy to manage and saves us time. It has much less complications.

We're using the community version. The tool is open source.

I also use PostgreSQL.

The tool helps us get the job done. It is not very complex. Overall, I rate the product a nine out of ten.