MySQL

We chose MySQL because of its open-source nature and its compatibility with various systems, languages, and databases. It is easy to use and fast. Additionally, it has been in the market for more than 30 years now which makes it a reliable option when compared to its competitors and other products available in the market.

Our original implementation of MySQL was to replace an Access database that had unfortunately been able to grow beyond its abilities and scope. MySQL seemed to offer all the benefits of Access (easy to set up, use and administer) with none of the downsides (reliability, fragility, poor performance) and was quickly implemented to replace it. Once the transition was made, we never looked back and have used MySQL in a range of other projects.

As I have been commenting in our company, we have solved our performance problems and responses obtaining speed in the queries occupies less disk space, in addition to its price and all the tools of great Scope it possesses.

We let go SQL server as We don't want to use Windows server and bare the cost of Windows licensing.

The primary reason we use MySQL instead of MongoDB is because we are in a large, legacy enterprise environment. MySQL works well and has all the necessary integrations with the various other software tools in our company's suite. Additionally, MySQL is a relational database which is a necessary feature for the environment I'm currently working in.

It was quite challenging to choose between these as they both have their pros and cons. But as far as we were concerned the decision to adopt the MYSQL database for our production was because it is an open-source language. This makes it very compatible with our needs and was the main reason for our adaptation.

MySQL is open source and reduces development costs drastically.

MongoDB has a dynamic schema for how data is stored in 'documents' whereas MySQL is more structured with tables, columns, and rows. MongoDB was built for high availability whereas MySQL can be a challenge when it comes to replication of the data and making everything redundant in the event of a DR or outage.

MySQL works properly, it gives us the most efficient data and the organization of the data yields an unsurpassed result in performance. And in the same way, in our case as a company, we have users from different offices that are in the same line of work since they can share and receive all the data if they are authorized.

I have evaluated MySQL Heatwave for some ETL pulls in our database to generate reports for stakeholders. It helped me to do so.

Microsoft SQL and SQLite i have used for different scenarios. SQLite is very small database which is more easy to work with low profile devices like mobiles. MySQL is not suitable for that level and MSSQL mainly comparable with MYSQL. MSSQL has complex installations and compatibility issues with many development platforms which MySQL provides flexible options and is highly compatible with different platforms.

So the main reason i would stack up Mysql from rest of the others is that it is open source which can be helpful for doing any POC on the products and learning new technologies and it is also compatible with all other softwares like Microsoft SQL serve and Postgre Sql

Cost related, is the biggest advantage.

it is cost effective solution and that time we were looking the good RDMS which can support the GIS based datatypes.

Its community edition is fantastic

Having used both PostgreSQL and Microsoft SQL Server, I can tell that MySQL performs admirably in a Linux setting. When compared to Microsoft SQL Server, the extra benefit is the minimal or nonexistent licence fee. We find that MySQL's programming interface is particularly useful because of our heavy reliance on it within the PHP framework. PostgreSQL has similar advantages but is less popular. As a relational database server, MySQL performs admirably for use with websites. It operates smoothly in any Linux setting and is easily modifiable using PHP.

Higher levels of security and can handle multiple connections simultaneously which is required for our clients work. It also supports XML format which we've had issues with SQLite handling - doesn't appear to support it.

SQLite - Is the goto DB for Mobile/Desktop Apps. Its not as elaborate as Mysql but since its a RDBMS it provides all the basic features and its lite. We use mysql at the backend and for desktop app we use SQLite

postgres - Its a formidable opponent. It is fast and reliable and is is an object-relational database. It is more suited for very complex processing as it has a very tight data integrity. For simple, read-heavy workflows, web based projects (almost all projects) mysql is a much better choice. Also writing and executing query on mysql based client is a easy job. Personally I find executing queries on PSQL terminal quite cumbersome.

I would say that in a Linux environment MySQL works great compared to both PostgreSQL and MS SQL. The added benefit compared to MS SQL is the low or absent licensing cost. As we use it mainly from PHP the programming interface is great for MySQL. PostgreSQL has many of the benefits, but is a bit less used.

I have also used Microsoft SQL Server. It is quite similar to MySQL. However, MySQL has always been my first choice, I have been using it for a very long time. I have also worked with PostgreSQL in a DevOps project. It is good too but a bit hard to learn and understand.

MySQL is relatively easier to use and than PostgreSQL or SQL Server; it's also cheap to use in production compared to SQL Server. For a beginner who wants to ship something quickly, MySQL is really suited for it.

Before MySQL, our team was exploring and evaluating different options for a good RDMS (relational database management system) service. We explored Oracle, MSSQL, and Google BigQuery. Most of these are costly and not easy to maintain in the long run in terms of price especially when data is millions of records. It also supports storing millions of records/transactions.

MySQL is the best platform and it has the ability to even automate time-consuming tasks with a fully managed database service that has enhanced productivity. This tool keeps me up to date about any new features and through instant provisioning it is providing me fast delivery of the application.

A bit on the more complex side, but definitely one of the more popular solutions between our customers. As a stable alternative to the sometimes really pricy Oracle DB, it performed well for most of our not-database-heavy projects. It was a bit slower than no-SQL solutions on no-SQL tasks, but that's natural I think.

More lightweight and easier to learn than Oracle Database. Amazon DynamoDB is a better choice for big data.