Open Source Databases Threatening the Established Proprietary Market
-
I think the list is nothing but usage, not importance or usefulness. Honestly SQLite is pretty silly too, really. But when you consider just how many developers are running it just to do dev work, it is a lot. Access and SQLite are hard to enumerate because what does it even mean since neither of them is an RDBMS. Number of installations isn't the same as with an RDBMS. I wonder what they consider an "install" to qualify as an instance. Does every install of MS Office count for Access?
-
@thecreativeone91 said:
I've never seen DB2 in use..
Access Kinda seems a little out of place being in that list. It's okay Inventory Databases but much more than that it's limitations start to show.
West Corp used to have a few TB DB2 dbs... I have no idea what they are doing today though.
-
Even at IBM we didn't use DB2 for anything. MySQL and PostgreSQL were the only things in use.
-
Some of the longer lived Open Source Databases have become just as reliable, scalable, and user friendly as a lot of the commercial ones, I think.
-
@dafyre said:
Some of the longer lived Open Source Databases have become just as reliable, scalable, and user friendly as a lot of the commercial ones, I think.
PostgreSQL was giving Oracle a run for its money nearly a decade ago. PS is one of the most robust RDBMS available today.
-
@scottalanmiller I guess I need to add that one to my list of "to learn" things... I have a decent handle on running MSSQL and MySQL, but I haven't done any Linux failover with MySQL (don't plenty with Windows).
All of the FOSS applications that I learned on almost always seemed to use MySQL, lol.
-
@dafyre said:
@scottalanmiller I guess I need to add that one to my list of "to learn" things... I have a decent handle on running MSSQL and MySQL, but I haven't done any Linux failover with MySQL (don't plenty with Windows).
All of the FOSS applications that I learned on almost always seemed to use MySQL, lol.
MySQL / MariaDB are super popular for "low impact" usage where RDBMS probably isn't the right choice at all. They are lightweight and very simple. They are very good at things like handling typical websites database needs so are deployed in "trivial" roles where flat files would often do the trick. So you see them all over for things like WordPress, Drupal, little PHP projects, etc.
PostgreSQL is bigger, more robust, even faster, heavy duty Oracle / MS SQL Server competitor. It's the big, bad one that crushes just about everyone for RDBMS usage. And some big platforms, like Ruby on Rails, default to PostgreSQL not MySQL, so on more advanced projects it is the more common choice.
NoSQL is coming up quickly, though. For a lot of websites, MongoDB is a much better choice than either, for example.
-
The Node.js world tends to default to MongoDB. That's what we are using here. Outscales MySQL to a ridiculous degree.
-
@scottalanmiller https://www.meteor.com/ is another project that defaults to MongoDB. I just stumbled across that one a few days ago... I've been tinkering with it on C@C...
It seems interesting... admittedly, I haven't tried Node.js yet.
-
MangoLassi runs on NodeBB which runs on Node.js and MongoDB on Ubuntu
-
@scottalanmiller Yet another thing added to my "To Learn" list... I think my C@C server is going to be busy for a while, lol.
I'm testing out GitLab, OwnCloud, and everything else on my "To Learn" list that involves some flavor of Linux.
-
I've seen DB2 in use, we had so many machines with it holding customer information.
I was young then, and the memories have stayed with me.
The horror, the horror..
Then the company bought out another company which also had DB2 on some old Unix V knock off and some weird flat file thing on some PDP-somethings and we had to interlink the services and slowly transition everyone over.
