MySQL

In my current role as a software developer, we are using MySQL  in one of our old projects and in the new project as well, specifically for storing the device data from energy meters that send voltage, current, and other related information.

Basically, in our project, we have some APIs that our device calls. Once the data is received by the API server, we put it in BullMQ, and from BullMQ, we have set up the consumer that consumes the data and puts it in MySQL . Over MySQL, we built a dashboard to show the energy trend, users, and load averages both device-wise and in groups based on averages. We have created an analytics dashboard for the energy meters using MySQL.

In my work, we use materialized views by running a cron job over the server, utilizing it in two ways: one is from the application server that inserts data into another table for analysis, and the second is for making materialized views where we aggregate data such as daily averages for devices and groups of devices. Inside those views, we store group-wise metrics such as average current, average voltage, peak load, and average kilowatt usage per hour. We also present these views on our dashboard, providing users the flexibility to select devices and create views for real-time rendering.

We use Tata Communications as our cloud provider for this hybrid cloud deployment.

We have used MySQL from the start, as we had experience with it, and it is straightforward to set up and easy to manage with fewer people.

One of the best features MySQL offers is the materialized view that I use. Additionally, as it acts as a transactional database, its transactional properties are useful, although they are not much of a concern in our use case since we focus on device data.

The main feature we utilize in MySQL is the view, and I can say that it is the most valuable feature for our needs.

My organization has experienced positive impacts from MySQL, as it provides exceptional capabilities.

MySQL can be improved. While I do not see any significant improvements needed for MySQL in my use cases, I would consider it if any arise in the future.

I have been using MySQL in the industry for two and a half years, and I used it for approximately three years during my college time.

MySQL is stable.

MySQL's scalability is currently adequate, as we have increased operations from ten thousand to twelve thousand devices, and it is working fine for us, but we will monitor for any future issues.

We have not needed to reach out for MySQL's customer support, as the community provides solutions for any issues we face.

I have evaluated other options such as PostgreSQL , as it is better for analytics queries, but its primary and secondary index concept makes updates slower compared to MySQL, which leads us to use MySQL.

The initial setup for MySQL is straightforward and easy to manage with fewer people.

I have seen a return on investment with MySQL, as it allows us to manage with fewer employees, focusing on business logic rather than database management.

My experience with pricing, setup cost, and licensing for MySQL has been good.

I rate MySQL a nine out of ten. I choose nine out of ten because while there should always be room for improvement, I do not see any necessary adjustments in my use case since it is working fine.

I advise others considering MySQL to start with it if they have small teams and are undecided about which database to use. It is easy to set up and allows you to focus on your business logic initially without going for more complicated databases.

MySQL meets our expectations for our use case so far. We will see what the future holds. My overall rating for MySQL is nine out of ten.

I used MySQL  mostly for college projects. I have used Postgres, but for the use case that I utilized it for, I do not think it was interchangeable with MySQL . To be frank, I do not really know the nuances.

The best features with MySQL are the fact that it is open source and a relational database. The best part about using MySQL was that it was open source, so it was pretty easy to understand and get materials to learn.

MySQL has good documentation and online support. It is pretty good in terms of integrations, continuous integrations with different tools, and customization options.

MySQL was not scaled up, so I did not use the replication capabilities. I do not think MySQL's data security features were at an industrial level for my project, so I did not make use of them. I was mostly using indexes.

I would advise people thinking about using MySQL to look up if the indexing mechanism is useful for their needs and then accordingly select the right database, and also consider if relational databases make sense for their use case. MySQL uses B-trees, so indexing could not be relevant to some use cases.

I did not use any ACID compliant transactions with MySQL.

From my experience, MySQL was pretty stable.

I know MySQL has been used in industries by a lot of companies, which means that it is scalable. That is the extent of my knowledge. It should be good because MySQL has been used by industries. I know Facebook uses it.

I would rate the documentation and online support a 10 out of 10.

I do not deal with Oracle products anymore. That was just a one-time thing that I had for college.

Unfortunately, I do not deal with AWS , Google products, or Azure  products because they are usually paid.

MySQL is a very useful database which is used by a lot of companies, so it should be really good. I mostly dealt with MySQL in the last 12 months. My experience with MySQL overall was pretty good. I would rate this review a 10 out of 10.