Slashdot Mirror


Oracle's CTO: No Way a 'Normal' Person Would Move To AWS (zdnet.com)

Amazon may have turned off its Oracle data warehouse in favor of Amazon Web Services database technology, but no one else in their right mind would, Oracle's outspoken co-founder and CTO Larry Ellison says. From a report: "We have a huge technology leadership in database over Amazon," Ellison said on a conference call following the release of Oracle's second quarter financial results. "In terms of technology, there is no way that... any normal person would move from an Oracle database to an Amazon database." During last month's AWS re:Invent conference, AWS CTO Werner Vogels gave an in-the-weeds talk explaining why Amazon turned off its Oracle data warehouse. In a clear jab at Oracle, Vogels wrote off the "90's technology" behind most relational databases. Cloud native databases, he said, are the basis of innovation.

The remarks may have gotten under Ellison's skin. Moving from Oracle databases to AWS "is just incredibly expensive and complicated," he said Monday. "And you've got to be willing to give up tons of reliability, tons of security, tons of performance... Nobody, save maybe Jeff Bezos, gave the command, 'I want to get off the Oracle database." Ellison said that Oracle will not only hold onto its 50 percent relational database market share but will expand it, thanks to the combination of Oracle's new Generation 2 Cloud infrastructure and its autonomoius database technology. "You will see rapid migration of Oracle from on-premise to the Oracle public cloud," he said. "Nobody else is going to go through that forced march to go on to the Amazon database."

6 of 253 comments (clear)

  1. Re:Lying like an oracle sales rep proper by Anonymous Coward · · Score: 4, Informative

    "The only notable exception is Amazon"

    Of course I meant Azure :-)

  2. Re:Wow is Larry ever tired of being wrong? by jimtheowl · · Score: 4, Informative

    Coincidentally, I learned about Postgresql after spending countless man hours trying to do things with Oracle the hard way.

    Linking to C for instance; Oracle's way of doing this was to use a preprocessor that generated large amount of untraceable code. Postgres just had a proper API implemented in a library.

  3. Re: Wow is Larry ever tired of being wrong? by datavirtue · · Score: 5, Informative

    "For software development things like the "readers block writers" approach of SQL Server gives you a ton of headaches that just "work out of the box" with Oracles locking model of only writers blocking writers."

    False. SQL Server supports Oracle style locking models and more/better alternatives--out of the box. Oracle is relying on thier locking model for performance and devs have to be cognizant of it. SQL Server default is for maximum data safety. Flip a bit and you have Oracle style lock model.

    --
    I object to power without constructive purpose. --Spock
  4. Fuck Oracle by GrBear · · Score: 3, Informative

    Sorry, I have a great hate on for.. our company uses Netsuite, which is owned by Oracle. It's a steaming mess, and even though we pay over $3k a month for the service, when I need support I get told, "sorry, that's not a defect, check the online documentation".. which is complete shit.

  5. Re:I mean, I kinda get it by Anonymous Coward · · Score: 0, Informative

    S3 is the only really difficult mainstream thing to migrate away from. Most other services are thinly-wrapped repackaging of existing OSS alternatives:

    - SQS == ActiveMQ
    - Kinesis == Kafka
    - Dynamo == Cassandra

    Of course, if you're using something like AWS Lambda or baking in IAM policies or credentials in your code then you're doomed.

  6. Re: Wow is Larry ever tired of being wrong? by cornjones · · Score: 3, Informative

    Any time I read a comment like by the above, complaining about a well used stack with problems multiple times per week, all I can think is PEBKAC.

    I recently ran into a shop that was rebooting their win 2012r2 boxes Sunday nights bc they were 'unreliable'..

    People know what they are comfortable with. And, afaict, dont bother reading error messages they don't expect. (if anybody has managed to write an error message that people will read and correct based on, I would love to know your voodoo.) similar to how people alway blame the network.. (hint, it isn't the network)