4 ms·
The more I read stories like that, the more I wonder why companies use Oracle at all. Is it really just cover your ass, institutional inertial and people who d
by tomjen3 11y ago
The more I read stories like that, the more I wonder why companies use Oracle at all.
Is it really just cover your ass, institutional inertial and people who don't know better?
- raverbashing 11y agoThis but also their salesman playing golf with the CTO in a fancy hotel
- pionar 11y agoOk, let's take a hypothetical (though, VERY close to what I've seen). You're a SAAS company. Not a startup, a medium-size company that's been around for 20+ years. Your core software is close to 15 years old. It's 2.5 million lines of code (not that hard to do with "enterprise" software). You have somewhere around 75 TB of data in probably 500 individual customer databases (multi-tenancy was not thought of in 2002 when your core software was developed). This software expects Oracle to be the backend. You can either: 1. Sink time and money into engineering time to evaluate, choose, and implement a new DBMS, and pay for consultants, licenses (if you choose a proprietary one), hardware (you'll need some, because you'll have that weird in-between time as you're migrating your customers' data). You'll have to properly train your DBA's and developers (and ops people) on the new DBMS ($$). You then have to write proper ETL scripts, schedule downtime with your customers (who have nearly 24/7 operations and transactions), make the switch, hope everything went well, then repeat that for your other 499 customers. - or - 2. You can continue to pay Oracle, because you've got that in your budget every year, and it's not worth the hassle.
- gaius 11y agoBecause if you use it for what it's for, Oracle is very, very good. 10 years ahead of the competition, easily and remember there is no "cheap" or "expensive" in business, only worth the money, or not. But if you are just some schmuck developer who needs "a database" and you settle on Oracle and don't use all of its clever features because you've hidden it behind SQLAlchemy or Hibernate in an attempt to be database-agnostic, well then you're going to get taken to the cleaners, but it's your own fault.
- nemo 11y agoYes, Oracle's database is really very, very good, and if you know how to use it it's really powerful. I really did like working with it, but hope I never will again due to the company that sells it. While Oracle is powerful (and fast and scalable and feature-rich), if you get to know another enterprise RDBMS in depth you'll find that once you start leveraging vendor-specific features you'll get more power as well (perhaps not as much as Oracle, but still quite a lot), at the expense of vendor lock-in. Using an ORM or other abstraction layer to be DB agnostic for some businesses would be a better financial choice, since once Oracle's burned you, you can burn your bridges and walk away to something that might be technically less powerful, but will probably save you a lot of money. Vendor lock-in has its own costs. It depends on your scale and your plans to scale. Running large scale enterprise apps Postgres might be very risky (Postgres is getting better, though), but DB2 or another alternative might work as well and give you some leverage when the Oracle audit thugs come in to extort more money from you. While I know I am biased, I sincerely believe that Oracle the company is a money grubbing monstrosity that acts effectively as an extortionist to their customers (they aren't alone here, but stand out to the degree they push the envelope of greed, they're a good 10 years ahead of the competition). They ruined Sun/Solaris, they ruined MySQL (letting it wither when it could be much further along by now), they are doing very dubious things with Java, they hosed OpenOffice, and I need to stop at PeopleSoft because my blood pressure is raising - and are pretty much trying to be the MS of the 90s in the markets they are in, and being in a position to be able to walk away from a business like that is a very practical business decision.
- gaius 11y agoMy belief is if you can feasibly write your app with an ORM then you should just use Postgres. If you can't, because you need $feature that the ORM doesn't manage, then buy the most powerful database you can afford and actively look for opportunities to exploit every bit of the functionality that you've paid for. The truth is being database agnostic is wildly overrated; in practice any organization will go through 10 languages before they decide to change their database, and no-one in their right mind cares about designing an app that is "language agnostic". You wouldn't start out in a language that supports, I dunno, closures, then deliberately not use them just in case you wanted to switch to another language in a couple of years.
- davidgerard 11y agoOracle is a very good database indeed. You give it data, it gives it back utterly reliably and very fast. You send it crappy queries, it optimises the hell out of them. It's clunky and laborious to program and administer, but it works superlatively. The problem is literally everything else about dealing with Oracle in any manner. There used to be no real alternative. Fortunately, almost everyone with Oracle doesn't need something that ridiculously powerful, and Postgres is in fact the 99% solution.
- marcosdumay 11y ago> You give it data, it gives it back utterly reliably and very fast. Well, it does... if you massage your data correctly, cause Oracle does not support many formats, and if it does not return some cryptic error for a condition that you'd never expect to exist in a DBMS.
- davidgerard 11y agoThis is true. If it's still the 1990s, you can live with this. In 2015, its annoyance factor can get a bit much.