I think your most demanding use of databases was in tiny environments with tiny datasets and relaxed performance metrics compared to my own experience in designing systems that include databases.
MySQL and Oracle DB are totally different beasts for totally different needs, even if they’re both relational databases.
Further, the Oracle DB predates MySQL.
MySQL was created exactly because at the time there were either these massive Enterprise Class behemoth expensive databases such as Oracle DB and IBM’s Db2 or stuff like Access and hacked Excel sheets being used as “databases”, so there really wasn’t a proper database for things like inventory systems for small and mid-sized companies - they either used Access which was a joke (didn’t even had Transactions, so prone to get corrupted) or they paid a lot for licenses for the big databases which also required expensive machines to run them on.
One could say that MySQL made a lot of the modern Internet possible because it was Open Source and ran on Linux so you could for free make a dynamic website (say, a small online store) on top of a stack with it at the bottom (and Apache at the top and some custom middle layer in something things like PHP - remember that these were the 90s and Python only became popular later) on a pretty basic Linux server somewhere and that was enough until you got really big. You could do it with Oracle DB at the bottom also, but it was expensive and not really worth it unless you were serving tens or hundred of thousands or requests per minute.
That said, I agree that Oracle DB wasn’t revolutionary, it just worked well with all kinds of loads, even extreme ones, as long as you knew what you were doing.
The point I was making was that the Oracle DB was the only decent product Oracle ever created, not that it was revolutionary.
They didn’t make Mysql if that’s what you’re referring to and Oracle DB was nothing revolutionary.
I think your most demanding use of databases was in tiny environments with tiny datasets and relaxed performance metrics compared to my own experience in designing systems that include databases.
MySQL and Oracle DB are totally different beasts for totally different needs, even if they’re both relational databases.
Further, the Oracle DB predates MySQL.
MySQL was created exactly because at the time there were either these massive Enterprise Class behemoth expensive databases such as Oracle DB and IBM’s Db2 or stuff like Access and hacked Excel sheets being used as “databases”, so there really wasn’t a proper database for things like inventory systems for small and mid-sized companies - they either used Access which was a joke (didn’t even had Transactions, so prone to get corrupted) or they paid a lot for licenses for the big databases which also required expensive machines to run them on.
One could say that MySQL made a lot of the modern Internet possible because it was Open Source and ran on Linux so you could for free make a dynamic website (say, a small online store) on top of a stack with it at the bottom (and Apache at the top and some custom middle layer in something things like PHP - remember that these were the 90s and Python only became popular later) on a pretty basic Linux server somewhere and that was enough until you got really big. You could do it with Oracle DB at the bottom also, but it was expensive and not really worth it unless you were serving tens or hundred of thousands or requests per minute.
That said, I agree that Oracle DB wasn’t revolutionary, it just worked well with all kinds of loads, even extreme ones, as long as you knew what you were doing.
The point I was making was that the Oracle DB was the only decent product Oracle ever created, not that it was revolutionary.