My employer has a database committee and we’ve been discussing different platforms. Thus far we’ve had people present on SqlLite, MySQL, and PostreSql. We currently use the Microsoft stack so we’re all quite familiar with Microsoft Sql Server.
As a part of this comparison I thought it would be interesting to create a small reference application for each database platform to explore the details involved in working with it.
First: does that idea make sense or is the comparison require going beyond the scope of a trivial sample application?
Second: I would imagine each reference application having a discrete but small set of requirements that fulfill many of the scenarios we run into on a regular basis. Here is what I have so far, what else can be added to the list but still keep the application small enough to be built in a very limited timespan?
-
Connectivity from the application layer
-
Tools for database administration
-
Process of creating a schema (small “s” schema, tables/views/functions other objects)
-
Simple CRUD (Create, Retrieve, Update, Delete)
-
Transaction support
Third: has anyone gone through this process, what are your findings?
Actually learning capabilities of each RDMS is more crucial. Because it depends on the application. If you need spatial data capabilities PostGIS with PostgreSQL is better than MySQL. If you need easy replication, high availability features MySQL seems better. Also there are license issues. A link for comparison here. All has strengths and weaknesses. First get the requirements of your project or projects than compare it with list the features of the RDMSs you pick and decide which one to go.