I knew some Oracle engineers back in the day. They were sharp. I hope they made their millions and got the heck out of that place.
The people who sign the cheques and listen to their salespeople.
I never got to hear the Oracle rep's side of the phone conversation, but everyone within 50 feet of the CIO's office got to hear his.
"Fine! You want to fuck me on these licenses! Go right ahead! And then I'll turn around and fuck you by throwing you out of our datacenter!"
Organisations do not realise the risk they face with closed source software. You are basically at the mercy of your vendor.
I believe any a CTO/CIO worth their salt would require motivation on why to use proprietary software vs open source. Is there absolutely no alternative?
As an engineer, I like to think of this primarily social problem like trying to focus a huge, distributed system architecture upon as few languages and platforms as possible. With most enterprises having grown through dozens, maybe hundreds of mergers they have a huge zoo of different stuff to support culturally. You could try integration approaches like message buses and such, but there's a lot of people overhead involved there and it gets really ugly when everyone disagrees upon the message bus (and in sufficiently large groups, conflict is inevitable).
Really if your worried about becoming attached to a particular technology, you should choose from the beginning to build a heterogeneous environment, and require all your in house development to adhere. In the beginning it might be painful to assure that your software stack runs on two different databases/OSs/ec, but once the abstractions are built up it will likely result in a more stable environment, and ease porting to a third should one of your original choices die.
This then raises issues of compatibility with your customer's environments. The configuration matrix that you'd need to test is tedious (read: costly) in traditional software releases compared to SaaS where you're free to make a lot of decisions independent of your customer and not everything can be automated (anyone that's deployed automated tests against TN3270 terminals with a lukewarm IQ QA department is right to challenge this). Then there's longevity. What happens when your biggest paying customer wants you to stay on IE 8 until 2025 (not an exaggeration)? Want to create yet another customer-specific branch? Eventually you wind up needing a test environment that matches exactly what that customer has and paying contractors to maintain that dead-end tech stack and doing that for every customer. That is quite common and also quite costly but not needing much talent, so the washed up maintenance engineers go here at less than mediocre compensation to cut costs. That's zombie software for you - the soul and spirit of engineers are gone and its corpse is animated by money by a cruel master that cares little for its past life.
Do they? Isn't it all just rolling the dice on algorithm trivia at this point?
> Amazon is internally use to being frugal, and so pricing wars are not going to hurt them.
eye roll.
> Oracle is use to charging a arm and a leg for their products.
Doesn't mean they don't know how to price a product like this.
> Amazon shareholders are already use to the company not being profitable, where as Oracle shareholders are not
Who says oracle is going to blow all their profits?
They may be used to being frugal, but that is not at all reflected in AWS pricing, which is ridiculously high across the board.
I make a lot of my income cutting peoples infrastructure costs by optimising their setups, and a lot of it involves moving people off AWS (I also move people onto AWS when they have needs that are actually best met there - there are lots of AWS services I love, but they are expensive) to save money. I can generally price my services at a few months worth of their savings.
Competing with AWS on price isn't the hard part. The challenge is the amount of people that either don't care, or think that AWS is cheap without having done realistic comparisons.
But for Oracle, those are exactly the type of customers they have built their entire business around selling to.
But their margins should be large enough, and have been for so many years, that they should have been able to take that into account and adjust expansion accordingly.
I'm more inclined to think that they have simply decided to milk it while they can. I rarely meet people who have any clue what their infrastructure choices actually cost them and what they would pay elsewhere, and I regularly have conversations about how much people believe they'd save by moving to/from provider X where it transpires that said person hasn't even tried costing it out but are certain they'll save money. I also regularly talk to IT departments that have no kind of budget or forecasting in place for their hosting requirements. The state of budgeting for server infrastructure is simply shocking. In that kind of environment, if you price based on actual cost, rather than based on whether or not people believe you're expensive, you're leaving money on the table.
1. What's constraining AWS's growth capacity? Isn't it simply a matter of stamping out AZs and DCs?
2. Why would Amazone create a pricing structure which encourages new entrants into the field? Contrast local retail in which defunct firms continue to sit on, and extend, real-estate leases, strictly to prevent other companies from growing into the market they've abandoned. See Dominicks / Anderson grocery stores in the Chicago area, in which seventy-two stores are being leased, at a cost of ~$1m/year, each, to prevent competitors from occupying the space:
http://www.chicagotribune.com/business/ct-vacant-dominicks-s...
(This works in part because rent is only a small part of the operational cost of a grocery store: electric power, labour, maintenance, and of course, groceries, are required if you're actually utilising the space.)
Because the primary entrant threats were not going to be dissuaded by low price competition. Specifically Microsoft and Google. Both are hyper cash and income rich and under no circumstances did they want to cede the cloud computing universe to Amazon. Fundamentally it's the exact same reason AWS stopped trying to compete so intensely on price cuts quite a while back now.
Put another way, if you're going up against Google, Microsoft, IBM, Oracle - speaking hypothetically it's better to own 1/3 of the market and print significant operating income, than to own 1/2 of the market and barely make money. That operating income is responsible for roughly doubling the value of Amazon's share price (the stock took off like a rocket after it became clear AWS was going to be a cash-cow).
1.) Amazon has a much higher bar for hiring talent, than Oracle does.
2.) Amazon is internally use to being frugal, and so pricing wars are not going to hurt them. Oracle is use to charging a arm and a leg for their products.
3.) Amazon shareholders are already use to the company not being profitable, where as Oracle shareholders are not.