|
Oracle已经过时？(5) However, time and time again now I come across situations where the database is considered just part of the underlying platform and all the real activity takes place on the mid-tier and in the application, and if you've going to do that, you might as well use mySQL or Access. Also (and this is particularly pronounced in the BI and OLAP world, and will be more so when Yukon comes out) rival databases are catching up with Oracle in terms of features, and in most cases have a better "out of the box" experience that doesn't scare off curious first-time users of the database. I think like in any walk of life, it pays to hedge your bets, and if you speak to most advocates of Oracle technology (including many of the Oaktable members) they also have a good understanding of rival RDBMSs, and in some cases recommend them in preference to Oracle. Also, it depends where you are in your career - I'm 36 now and working with Oracle more or less for all of my IT career, and in all probability will continue to work with databases for the rest of my time in the industry. If, however, I was just starting out, I'd probably focus more on Java or .NET application coding, look more at "mid-tier" issues and spend less time on the database, storage and the operating system. Still, having said that, I still come across AS/400-based applications, and consultants who still make a packet looking after these supposed "legacy" systems, and don't have to spend all their time recertifying and getting their heads around concepts such as "grid computing" and "service-orientated architectures", so it could just pay to sit it out and let everyone else fight it out over the next new great thing.
|
