Answer the question
In order to leave comments, you need to log in
MySQL vs other DBMS - which is better?
Hello.
A bit of background: as a graduation topic, I received the development of one program for calculating certain indicators and printing documents. I must say right away that I was not very good at programming and I was interested in learning everything (by the way, I chose the c# language).
I chose mysql as a DBMS (a friend advised), and it’s free and all that ... You
can say that I made the program, and then the person who will sit on the defense of diplomas decided to see what we were doing. When the teacher heard that I was using mysql, she immediately stated that the subd was not very old, old (namely old) and all that ... I was not ready for such conversations, I could not answer anything intelligible to her and justify my choice.
Now I decided to justify my choice of a free DBMS, I started comparing it with Postresql ... But for some reason, everywhere they first give a lot of Mysql pluses, and then they say to look at Postresql - a very good project and it's better to use it.
The question is, if Mysql is really a bad choice at the moment, then what to choose for development so that you can easily justify your choice (ready, probably, even to consider paid DBMS)? If, nevertheless, it has its positive features, bring them, please.
I would be very grateful for any useful information!
PS If it's better to redo it, please advise the options for which it will be as easy as possible to switch to a new DBMS. And of course, justify all this in the graduation project.
Answer the question
In order to leave comments, you need to log in
The teacher tells you so, because there is such a thing - the Microsoft technology stack. And for many, C# should only dock with MSSQL, but not with other databases. This really makes sense when the project is very large. Roughly speaking, the language and database developed by the same company are quite tightly integrated. But this does not mean that MSSQL is the only and most reasonable choice.
I write in C# myself and use MySQL instead of MSSQL. Why:
1. MySQL runs on any OS (does not require a paid Windows license).
2. Full featured MySQL is free unlike.
3. Lightweight, does not require powerful hardware. As a result - faster on a similar hardware.
4. MySQL hosting on every corner.
5. The choice of engines for each table and each case.
6. Full text search (in MyISAM).
7. There are forks that guarantee normal development if Oracle decides to do something bad. Well, what can I say, OpenSource.
At the same time, modern MySQL supports many features of modern databases: View, triggers, functions, stored procedures, events, subqueries.
subd is not very old (exactly old) and all that ...
Did you offer an alternative? How to do that would not have been the old suggested? Or is there no one to shut him up and he began to shine with his mind?
It seems to me that either the teacher is old, or you are not saying something. For example, what kind of software? Maybe you need NoSQL there and the teacher says that Mysql is "old" for solving a new type of task, since it was designed a long time ago and is not suitable for your project due to architectural features.
On mysql.com on the first page "10 reasons to choose mysql". Translate - and you will have arguments)
www.oracle.com/webapps/dialogue/ns/dlgwelcome.jsp?...
At the expense of the old dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5 -3... here's an update to the January 1, 2014 release. Now there is version 5.6, and 5.7 is also being prepared.
Well, the argument "and all that" is of course difficult to find an answer.
Switch to MariaDB, it's much newer and you won't have to rewrite anything :-)
Look towards muscle alternatives/forks - PerconaDB, MariaDB.
You can hint to the teacher at the "old" Oracle, which, oddly enough, still works with servers in the whole large enterprise, like banks or opsos.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question