Amazon Cloud Chief Jabs Oracle: 'Customers Are Sick of It' (cnbc.com)
It's no secret that Amazon and Oracle don't see eye to eye. But things are far from improving, it appears. From a report: On Wednesday, two months after Oracle co-CEO Mark Hurd called Amazon's cloud infrastructure "old" and claimed his company was gaining share, Amazon Web Services chief Andy Jassy slammed Oracle for locking customers into painfully long and expensive contracts. "People are very sensitive about being locked in given the experience they've had the last 10 to 15 years," Jassy said on Wednesday on stage at Amazon's AWS Summit in San Francisco. "When you look at cloud, it's nothing like being locked into Oracle." Jassy was addressing a cultural shift in the way technology is bought and sold. No longer does the process involve the purchase of heavy proprietary software with multi-year contracts that include annual maintenance fees. Now, Jassy says, it's about choice and ease of use, including letting clients turn things off if they're not working.
Oracle: We own our software ... and our customers.
Amazon: We own our software ... and we are our customers' assistants.
Since when is SaaS not all about lock in?
I like the fight: competition in action. I wish telecoms would bash each other over forced bundling, lousy reliability, lousy customer service, etc. etc. etc. etc.
Table-ized A.I.
Oracle is such an entrenched, parasitic, rent-seeking corporate shit pile compared to most of the industry that they make even staunchly conservative capitalists tempted for a split second to raise the sickle and hammer after dealing with them.
hell be dead by then yo
Speaking of old, why not hook up a mainframe to the "cloud"? It's all built around I/O, partitioning and billing the user anyway.
Let's have a single computer datacenter. We can achieve the classic vision of one computer per continent.
I believe curious people might try to use it. I know there are emulators and a freeware IBM OS version from before I was born, so it is certain that millions of people never had the chance to try doing something, anything at all with a mainframe.
I have a pitch for it : "The state of the art in NoSQL and consolidation."
Yeah, fuck these rich cocksuckers, and if you care about your business or data at all, do not use either of them.
"No longer does the process involve the purchase of heavy proprietary software with multi-year contracts that include annual maintenance fees. "
I guess the two sides really don't know how each other works....
Amazon route53 is amazing, cheap, and scales up to infinity for whatever you might need. (This earns universal praise from everyone I've talked to who's used it)
Google's cloud DNS products are cheap and reliable and fast and also scale extremely well.
Cloudflare has some amazing products that are built from from the ground up to scale well and tie in well with their CDN products- Which really go hand in hand with the way modern web application work anyway.
DNSMadeEasy is a braindead easy and inexpensive. Worth a look if you don't need anything super crazy. I've migrated a few small scale DYN accounts to these guys (a few dozen to few hundred records) to these guys. Its a snap. Import a text file or set up a zone transfer. Slam bam thank you mam and you're ready to point your domains to new dns servers in minutes. Zero problems and 1/10th the cost.
DYN was amazing six or seven years ago but their pricing has gone up and their product hasn't chance much at all. Their web interface is disjointed and clunky and the Oracle acquisition just seems to have them standing in place to see what happens next. Today there are better alternatives.
I see two ends of the spectrum: ... tons of really cool stuff, all of it industry-grade software.
Want an own DB?
Use FOSS.
MariaDB, MySQL, Postgres, Mongo, Couch,
I see virtually no usecase at all for non-FOSS DB technology in a fresh project these days.
Want to do the cloud DB thing? ... and probably is.
Use Google Spanner.
That's what Oracle should be afraid of
We suffer more in our imagination than in reality. - Seneca
I deal with so many functionality points in Oracle Documents Cloud (aka, Oracle Content) that I'm not even sure what functionality has actually shipped and those that are about to be released in a planned update, so I wont comment on what's there or about to get there.
But I can tell you it's a whole lot more than a mere document repository.
While licensing for that (say the iOS client) is yearly (and not lock-in), once you get going with the product line, it's a bit difficult to move this data off to another service because you loose all data integration with other processes (whichever they may be that I'm not comfy discussing right now).
When a large company moves such infrastructure, the biggest cost is data migration (there are some Oracle groups specialized in that).
From my perspective though (the iOS client for Documents Cloud), we work hard on new feature and integration. We deal with 4 different server infrastructures behind the scene to link up your data. And despite the cloud offering, we're still working on On Premise where YOU control storage.
Not going to comment on Amazon's infrastructure but I was not happy to see my Netflix go when S3 had a flat tire. :-)
My opinion is my own. Not talking for Oracle (my employer) nor am I a representative.
it's a bit difficult to move this data off to another service because you loose all data integration with other processes
And this is why, in general, tight integration across processes and functions can be a horrible,horrible liability as well as an asset (hello SAP). One where the downsides of lock-in and migration issues far outweigh the benefits of being integrated (hello Sharepoint). When there is a huge data migration effort involved in moving to the new environment, that's a hint that moving off the platform may well be even more painful.
If construction was anything like programming, an incorrectly fitted lock would bring down the entire building...
Java is even older than AWS! Should I stop using it?? I'm so confused!
Andy Jassy is almost correct, except that he's listing all the benefits of open source instead of them being 'cloud' benefits.
On a long enough timeline, the survival rate for everyone drops to zero.