MySQL is a popular open-source relational and embedded database, now owned by Oracle.
N/A
Neo4j
Score 8.8 out of 10
N/A
Neo4j is an open source embeddable graph database developed by Neo Technologies based in San Mateo, California with an office in Sweden.
$65
per month
SQLite
Score 8.0 out of 10
N/A
SQLite is an in-process library that implements a self-contained, serverless, zero-configuration, transactional SQL database engine. The code for SQLite is in the public domain and is thus free for use for any purpose, commercial or private. SQLite is one of the most widely deployed databases in the world.
N/A
Pricing
MySQL
Neo4j
SQLite
Editions & Modules
No answers on this topic
Aura Professional
$65
per month
Community Edition
Free
Enterprise Edition
Contact Sales
Aura Free
Free
Aura Enterprise
Contact Sales
No answers on this topic
Offerings
Pricing Offerings
MySQL
Neo4j
SQLite
Free Trial
No
Yes
No
Free/Freemium Version
No
Yes
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
—
More Pricing Information
Community Pulse
MySQL
Neo4j
SQLite
Considered Multiple Products
MySQL
Verified User
Engineer
Chose MySQL
MySQL is a standard across many industries and is familiar to most developers as a result. When comparing to something like MongoDB, most developers are more familiar and comfortable with MySQL. When comparing to something like Oracle, MySQL clearly wins in the expense …
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.
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 …
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 …
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 …
MySQL offers best conditions for a rapid adoption at the organization. Also because it's free software, you can scale up in implementations without worrying about licenses fees.
MySQL performs very well and has a great feature set. It gives the user, developer, and DBA a lot of bang for no bucks. It is efficient, cost-effective, and doesn't require other specialized hardware or software to run. Microsoft SQL Server generally only works on Windows. …
Neo4j
Verified User
Employee
Chose Neo4j
For easy query language and better graphical representation on small dataset
Also easy to set up and handle on the server.
On top of that Neo4j also provides an API support to interact through any system.
We looked at other traditional RDBMS products, but found them to be cumbersome to deploy. They take up more space, and consume more computing resources than SQLite does. While the performance or direct integration to our primary applications may have been better or easier if we …
SQLite is considered better against these two depending on the needs and phase of the project. If we require a lightweight yet reliable database which should also be portable across different platforms and speed is the most important part of the query and data security is not …
I think there is no real competition between them. In "SQLite" you can hear "light" when you don't need to store a big amount of data and when you need something easy to deploy, SQLite is a good choice, I didn't find those qualities in other database systems I knew.
MySQL is best suited for applications on platform like high-traffic content-driven websites, small-scale web apps, data warehouses which regards light analytical workloads. However its less suited for areas like enterprise data warehouse, OLAP cubes, large-scale reporting, applications requiring flexible or semi-structured data like event logging systems, product configurations, dynamic forms.
Neo4J is great for creating network graphs or illustrating how things are related. It is also good for finding individuals or things that have greater influence than others in a system. It is not appropriate if you have standard data sets that can be analyzed using conventional methods or visualized using Tableau, for example.
SQLite is a lightweight and efficient database management system. With SQLite, performance increases as memory are added. It's reliable and well-tested before release. SQLite handles memory allocation and I/O errors gracefully. SQLite provides bug lists and code-change chronologies. All bugs are disclosed, and it's compatible with iOS, Android, MAC, and Windows. SQLite is open-source, allowing developers to tailor it to their specific needs.
Mature Query language, I found Cypher QL to be mature in handling all sorts of problems we throw at it. Its expressive enough to be intuitive while providing rich features for various scenarios.
Native support for REST API, that makes interacting with Neo4J intuitive and easy.
Support for Procedures in Java, procedures are custom code that could be added to the Neo4J to write custom querying of data. The best part about the procedures is it could be invoked using the REST API. This allows us to overcome any shortcomings from their Cypher query language.
Nice UI and interface for executing the Query and visualizing the response.
UI access controlled by User credentials allows for neat access controls.
Awesome free community edition for small-scale projects.
Learning curve: is big. Newbies will face problems in understanding the platform initially. However, with plenty of online resources, one can easily find solutions to problems and learn on the go.
Backup and restore: MySQL is not very seamless. Although the data is never ruptured or missed, the process involved is not very much user-friendly. Maybe, a new command-line interface for only the backup-restore functionality shall be set up again to make this very important step much easier to perform and maintain.
One of the hardest challenges that Neo4j had to solve was the horizontal scaling problem. I am not updated on recent developments, but at the time of my use, I couldn't find a viable solution.
Neo4j does not play with other open source APIs like Blueprint. You have to use the native Neo4j API.
There wasn't a visual tool to see your data. Of course, third party tools are always available, but I would have loved something which came with the Neo4j bundle. I love that Docker comes bundled with Kitematic, so it's not wrong to hope that Neo4j could also ship with some default visualization software.
Although it is excellent at what it does, you should be really careful and plan accordingly if you know that your database is going to scale at a huge level because it is not suitable of databases which are of Enterprise level and demands top-notch security and protection.
If your project involves multiple people working on the same database simultaneously, then that becomes a big problem, because it only allows single write at one time. You really need to be forward thinking in a manner to predict if this database will cater to all the needs of your project.
The most common difficulty with this is the lack of some of the basic functionality which is present in the other premier databases like Joints, Stored Procedure calls, Security and permission grants. If you do require all those things then you are better off not using this software.
Lastly, if you are using this in an Andriod App development cycle then also your options are limited because it does not integrate with PostgreSQL and MYSQL.
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.
Learning cypher was super easy coming from a SQL background. Furthermore, the docs Neo4j provides on their website make it really easy to pull up a reference, guide or a quick example. The mac app they provide is also really well designed with good visualisation tools, with the ability to easily use colour, line thickness etc to help navigate your data.
I have given this rating cause its irreplaceable in some of the areas like no more installation need except from a single library. I find dialect is simple in use cases. its suitable for any professionals with various skill levels. its easily connect with various os and devices. very less maintenance or administration required.
We have never contacted MySQL enterprise support team for any issues related to MySQL. This is because we have been using primarily the MySQL Server community edition and have been using the MySQL support forums for any questions and practical guidance that we needed before and during the technical implementations. Overall, the support community has been very helpful and allowed us to make the most out of the community edition.
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.
Neo4j is a graph store and has different use cases compared to another NoSQL Document store like MongoDB. MongoDB is a bad choice when joins are common as existing operators for joining two documents (similar to tables in a relational store) as Mongo 3.5 use SQL like join algorithms which are expensive. MongoDB is a great choice when distributed schemaless rich document structures are important requirements. Cross document transaction support is not native to MongoDB yet, whereas Neo4J is ACID complaint with all its operations.
We looked at other traditional RDBMS products, but found them to be cumbersome to deploy. They take up more space, and consume more computing resources than SQLite does. While the performance or direct integration to our primary applications may have been better or easier if we had gone with a traditional RDBMS, the performance of SQLite has been more than acceptable. The performance and speed to deploy made SQLite a much more attractive option for us than a traditional RDBMS.
The active community has kept support costs low, further increasing ROI
The wide range of supported platforms and high level of compatibility has increased ROI by reducing time spent porting the database model to any platform specific solutions.
