The InfluxDB is a time series database from InfluxData headquartered in San Francisco. As an observability solution, it is designed to provide real-time visibility into stacks, sensors and systems. It is available open source, via the Cloud as a DBaaS option, or through an Enterprise subscription.
N/A
MySQL
Score 8.0 out of 10
N/A
MySQL is a popular open-source relational and embedded database, now owned by Oracle.
N/A
Pricing
InfluxDB
MySQL
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
InfluxDB
MySQL
Free Trial
No
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
InfluxDB
MySQL
Considered Both Products
InfluxDB
Verified User
Anonymous
Chose InfluxDB
We have looked around to find different options we had when we first started to move to cloud. At that time, the options we had is Google Cloud BigTable and InfluxDB. But quickly we realized that InfluxDB is the database specialized in time series database and performs better …
InfluxDB is much easier to initially setup and scale compared to Graphite (now known as Whisper). With a smaller team we found Graphite too much overhead that would make operational support a significant blocker or generation of technical debt.
To be honest, I didn't look at alternatives since InfluxDB performs very well if you can oversee the lack of security and HA features. But for all challenges, there is an easy solution which brings you forward (e.g. read load balancing can be achieved by using a common HTTPS …
Each of the products has its own merits and demerits. however since MySQL is a very good documentation and global community its easy to learn and apply in different stages for analytics work. compare to other data bases its simple for setup and work on it. MySQL is cost …
Rest all the big brand databases incure high licensing cost giving almost the same value that MySQL is giving being an open source database. Other databases like Oracle, MS SQL servers need extensive resource along with a huge team to manage those databases. However, thats not …
Selection of MySQL or Oracle SQL developer depends on various factors like timelines, requirements, features and data volumes. We are using both MySQL and Oracle SQL developer in our organization. MySQL is more suited for small applications with few thousand TPS and less users. …
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 …
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, …
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.
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 …
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 …
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 …
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 …
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 …
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
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 …
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 …
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 …
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 …
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 …
InfluxDB is a time series database and should be used in that intent. Each data ingestion streams should be properly configured to ensure optimal database performance. InfluxDB works very well but like any other databases requires maintenance and tuning. We have been using the TICK stack and are very happy with the results.
From my own perspective and the tasks that I perform on a daily basis, MySQL is perfect. It has a reasonable footprint, is fast enough and offers the security and flexibility I need. Everyone has their preferred applications and, no doubt, for larger data warehouses or more intensive applications, MySQL may have its limits, but for the area that I operate in, it's a great match.
Security: is embedded at each level in MySQL. Authentication mechanisms are in place for configuring user access and even service account access to applications. MySQL is secure enough under the hood to store your sensitive information. Also, additional plugins are available that sit on top of MySQL for even tighter security.
Widely adopted: MySQL is used across the industry and is trusted the most. Therefore, if you face any problems, simply Google it and you shall land in plenty of forums. This is a great relief as when you are in a need of help, you can find it right in your browser.
Lightweight application: MySQL is not a heavy application. However, the data you store in the database can get heavy with time, but as in the configuration and MySql application files, those are not very heavy and can easily be installed on legacy systems as well.
Small, but growing community - This database engine's community is much smaller than alternatives. This can make finding a DBA or support less easy, but not impossible.
Documentation could be improved - The docs for getting started don't effectively lead first-time users to understand how the underlying systems are designed.
Performance Analysis - There seems to be a lack of tools to give context to slow queries or other performance issues
Out-of-the-box security - The out of the box security is designed to operate in an internal network and is limited.
Although you can add the data you require as more and more data is added, the fixity of it becomes more critical.
As the demand, size, and use of the system increase, you may also need to change or acquire more equipment on your servers, although this is an internal inconvenience for the company.
InfluxDB is a near perfect product for time series database engines. The relatively small list of cons are heavily outweighed by it's ability to just work and be a very flexible and powerful database engine. The community and support provided by the corporation are the only areas I have little experience.
For teaching Databases and SQL, I would definitely continue to use MySQL. It provides a good, solid foundation to learn about databases. Also to learn about the SQL language and how it works with the creation, insertion, deletion, updating, and manipulation of data, tables, and databases. This SQL language is a foundation and can be used to learn many other database related concepts.
I give MySQL a 9/10 overall because I really like it but I feel like there are a lot of tech people who would hate it if I gave it a 10/10. I've never had any problems with it or reached any of its limitations but I know a few people who have so I can't give it a 10/10 based on those complaints.
We have worked with the InfluxDB support team a few times so far and it has been positive. Issues submitted are worked on promptly and we have good feedback.
The support staff is friendly, knowledgeable, and efficient. I only had to get part way through my explanations before they had a solution. They will walk you through a fix or actually connect in and fix the problem for you--or would if you can allow it. I've done it both ways with them. They are always forthcoming with 'how to do this if it happens again' information. I love working with MySQL support.
We have looked around to find different options we had when we first started to move to cloud. At that time, the options we had is Google Cloud BigTable and InfluxDB. But quickly we realized that InfluxDB is the database specialized in time series database and performs better than other options we have.
Each of the products has its own merits and demerits. however since MySQL is a very good documentation and global community its easy to learn and apply in different stages for analytics work. compare to other data bases its simple for setup and work on it. MySQL is cost effective and low risk choice for start up organization makes it more suitable for small to medium enterprises.