Apache Derby is an embedded relational database management system, originally developed by IBM and called IBM Cloudscape.
N/A
MySQL
Score 8.3 out of 10
N/A
MySQL is a popular open-source relational and embedded database, now owned by Oracle.
N/A
Progress OpenEdge
Score 9.0 out of 10
N/A
Progress OpenEdge is an application development environment to keep businesses running, that enables users to leverage technology advancements to more quickly deliver business applications.
N/A
Pricing
Apache Derby
MySQL
Progress OpenEdge
Editions & Modules
No answers on this topic
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Apache Derby
MySQL
Progress OpenEdge
Free Trial
No
No
No
Free/Freemium Version
No
No
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
Apache Derby
MySQL
Progress OpenEdge
Considered Multiple Products
Apache Derby
No answer on this topic
MySQL
No answer on this topic
Progress OpenEdge
Verified User
Engineer
Chose Progress OpenEdge
It has an embedded database, no need to make database connection. With concept of appserver in Progress Openedge we can handle any complex transaction processing system with ease. It is used by all old financial institutions to handle there bulk data and processing system. It …
If you need a SQL-capable database-like solution that is file-based and embeddable in your existing Java Virtual Machine processes, Apache Derby is an open-source, zero cost, robust and performant option. You can use it to store structured relational data but in small files that can be deployed right alongside with your solution, such as storing a set of relational master data or configuration settings inside your binary package that is deployed/installed on servers or client machines.
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.
I have had limited exposure to other development environments, but I have found Openedge to be well suited for the purposes that we are using it for. We have a windows client-server application that has been in use for over 20 years and has held it's age well. We also have a web based product using openedge appserver to access our backend code. The appserver functions well and we have been happy with it
Apache Derby is SMALL. Compared to an enterprise scale system such as MSSQL, it's footprint is very tiny, and it works well as a local database.
The SPEED. I have found that Apache Derby is very fast, given the environment I was developing in.
Based in JAVA (I know that's an obvious thing to say), but Java allows you to write some elegant Object Oriented structures, thus allowing for fast, Agile test cases against the database.
Derby is EASY to implement and can be accessed from a console with little difficulty. Making it appropriate for everything from small embedded systems (i.e. just a bash shell and a little bit of supporting libraries) to massive workstations.
Openedge databases are practically bulletproof, even when shot down abnormally. The offer complete transaction scoping, before imagining, and also after imaging for roll foward capability.
Openedge has a very powerful and easy to learn 4GL programming language that can be used in a traditional or object oriented manner.
Openedge also has powerful web services components, fully integrating both SOAP and RESTful web services.
Openedge is completely scaleable from 1 user to a fully distributed global enterprise solution.
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.
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 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.
SQLite is another open-source zero-cost file-based SQL-capable database solution and is a good alternative to Apache Derby, especially for non-Java-based solutions. We chose Apache Derby as it is Java-based, and so is the solution we embedded it in. However, SQLite has a similar feature set and is widely used in the industry to serve the same purposes for native solutions such as C or C++-based products.
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.
The decision to use openedge with our particular product was made such a long time ago that I certainly was not around to make the decision. And most of the other products that would have been compared at the time are likely no longer around. Which does speak to the longevity and benefits of this product. When you look back and see how long the same product has been going forward with constant improvements and remaining relevant without major disruptive changes, it is worthy of some credit.
Being Open source, the resources spent on the purchase of the product are ZERO.
Contrary to popular belief, open source software CAN provide support, provided that the developers/contributors are willing to answer your emails.
Overall, the ROI was positive: being able to experiment with an open source technology that could perform on par with the corporate products was promising, and gave us much information about how to proceed in the future.