4 ms·
oracle products aren't really products you can ditch in most cases. generally what it takes to get rid of them is to go out of business and be replaced by a bu
by kragen 3y ago
oracle products aren't really products you can ditch in most cases. generally what it takes to get rid of them is to go out of business and be replaced by a business that isn't an oracle customer. i had a very interesting thread about that dynamic on here with pamar three weeks ago, which will be very interesting reading for anyone who is wondering why people don't ditch oracle https://news.ycombinator.com/item?id=39397513 https://news.ycombinator.com/item?id=39397513
- pantulis 3y agoThanks for pointing that thread out!
- kragen 3y agoi'm glad you're enjoying it! i found it very educational
- le-mark 3y agoI think the missing piece from that exchange is the reality that a lot of surviving, legacy, mission critical applications is that they are generally internal to large companies and have grown over decades to encapsulate business processes for entire industries. Consider an application that has been under active development for 30-40 years by 10-100 developers. The cost to rewrite is staggering, and the risk of failure is huge.
- kragen 3y agoi agree with that point and i would add a link to your comment if i could still add to that thread
- konschubert 3y agoThat’s why it’s so important that competition is possible in a market. Such that legacy players with inefficient legacy technologies can be driven out of the market.
- geodel 3y agoAnd which is efficient modern technology taking its place?
- konschubert 3y agoFor oracle DB, it’s mostly Postgres I guess?
- kragen 3y agopostgres is adequately efficient technology from last millennium, but at the level of execution efficiency it's pretty much the same as oracle, maybe a bit worse more recent systems like impala, spark, kafka, cassandra, leveldb, influxdb, rocksdb, duckdb, monetdb, lmdb, sqlite, parquet, hbase, etc., are a lot more efficient at execution efficiency, though in many cases that's only 'up to such-and-such a scale' or 'above such-and-such a scale' or 'for such-and-such use cases'. there's a perhaps too comprehensive overview of the scene at https://github.com/newTendermint/awesome-bigdata https://github.com/newTendermint/awesome-bigdata but the big business inefficiency with oracle is not technical, it's the human problem of not having control over your core business processes or the ability to continue carrying them out if, when oracle says 'jump', you say anything but 'how high?'
- konschubert 3y agoDisregarding your list of "modern technologies" for a second, I think we agree on the core point here: Postgres may or may not be better than oracle DB. The sizeable advantage it has: you're not dependent on another company that will try to extract your margin as a fee.
- burningChrome 3y agoA smaller company I worked for a few years ago was migrating its old ERP legacy system and brought in some people from Oracle, SAP and Epicor. They decided to go with SAP, but I remember my boss in several lunch meetings saying that they didn't get a sales pitch from the other vendors as much as a litany of horror stories about why they shouldn't go with Oracle. It worked since my manager said he asked around and did his own research and wondered how they're even still in business since everybody he talked to said the same thing - whatever you do, do not go with Oracle.
- AtlasBarfed 3y agoHow does anyone in IT management not know that Oracle is poison? That blows my mind. I encountered two Oracle audits within 7ish years in the industry, and heard about others. If anyone goes to MIS school, there should probably be a contracts day somewhere in that curriculum, and "don't use Oracle" should be the first bullet point. Maybe in the 80s and 90s without the internet it might be more hush-hush. But this is now two decades of aggressive Oracle audits. Two decades is a LONG TIME for companies to get off of a vendor. And now there's Postgres with, what, 30 years of engineering into it? Honestly if your database scale exceeds Postgres, you should be on Cassandra or other specialized database that will actually scale to really large sizes, not some weirdo hyper-hardware Oracle setup. Virtually every large org has a very involved process for vendor selection. HOW DOES ORACLE SURVIVE THESE? How does any IT organization not have a standing policy of "generally don't use oracle unless you absolutely have to"?
- kragen 3y agopostgres dates from 01974, it used to be called ingres, so it has 50 years of engineering, not 30. the 'post' is from when they added 'object-oriented' features to make it 'post-relational' as i understand it, oracle mostly sells to executives above it management, but there are also lots of executives in it management who aren't as concerned about the survival of their company as they are their own careers. it's hard to point to cases where company failure can be specifically pinned on oracle licensing fees, but since a company running on oracle can never switch away, ultimately there's no reason for oracle to leave any profits for the company shareholders when they could simply extract them in licensing fees. unless the company has pre-existing licensing contracts in place, i guess, and successfully defends them — which it won't be able to do if it fails oracle's licensing audit, and obviously copyright infringement is ubiquitous in every company, so most will fail, and then oracle can alter the deal