Oracle Is Bleeding At The Hands Of Database Rivals
techcrunch.com
techcrunch.com
There's no single Postgres dev, it's been community-driven from the start and the various postgres companies mostly provide support. So there's nobody to pay $1bn to really.
If you look at the contributors page[0], out of 6 "core devs" there are 5 different companies, with EnterpriseDB being "overrepresented" at 2 core from the company, plus a pair of "major contributors" out of a truckload.
And these people are probably Postgres devs first and foremost. Not Tom Lane or Josh Berkus, but even if Oracle bought out EnterpriseDB they might just cash in and work on Postgres from an other company.
[1]http://www.informationweek.co.uk/software/enterprise-applica...
- sql server
and
- reliable
don't really belong in the same sentence.
If your friends don't experience any problems, I would venture to guess they must be running small databases, or databases where the workload is 90% reads 10% writes.
http://msdn.microsoft.com/en-us/library/ms173763.aspx
In addition to setting a database level default, you can even have it behave differently per connection. Snapshot isolation will never lock, period.
SQL Server is actually quite capable, and has the fantastic tooling that cheaper alternatives like PostgreSQL lack.
It's not what I would have picked (I come from a Linux and Oracle background), but I've been very impressed.
The DBs are often very write intensive on the master, with as much reading as possible done on slave databases, with tables heavily normalised to try and reduce the disk performance hit.
Most of the extremes of the setup are there for legacy performance reasons - The newer systems using SQL Server 2008 or 2012 and SSD drives generally don't need it, and we're moving towards a less normalised setup.
Also, since the entire discussion started by me questioning the reliability of sql server, can you say how many days your database server stays up between reboots?
Oracle's query interpreter, for example, is extremely anal, you have to commit everything and Oracle is likely to reject your queries if they are slightly off, which helps catch errors.
SQL Server follows more of a "Do What I Mean" approach, even going as far as to perform implicit type conversions for you, which is fine until it guesses wrong. Then, instead of rejecting your query, it screws up your data.
And don't tell me I can configure it to behave differently, it should work correctly out-of-the-box.
That said, there will always been a need for the product Oracle provides in the largest of companies. NoSQL isn't going to be running reports on the fortune 500 anytime in the next two decades, and neither is Postgres, as much as I like it.
Death by a thousand cuts will probably still be profitable for decades.
Oracle will forever dominant HR, Payroll, SCM, Billing, FM etc type systems where more often than not they have custom software on top of it that has been built exclusively for Oracle. There is simply no good reason to switch. If anything the threat to Oracle will come from hosted apps e.g. Salesforce.
But what I've been seeing in our company is MongoDB dominating front end web apps and Datastax/Cassandra for more of the big data, analytics type workloads.
Oracle should be far more concerned with Amazon Web Services.
Big companies don't want to house large IT infrastructure anymore. It seems too costly in the long run and benefits are difficult to explain to the board.
Consequently, you already see companies moving what was before considered core infrastructure to the cloud and the trend is probably going to increase.
Deploying a VM on EC2 or Azure is easy, quick and cheap enough considering you don't have to house as many talents as before in the IT department. As companies move to cloud based services, they don't deal with databases anymore, the people providing the solution (we don't even talk about software anymore, that's the current level of abstraction) does. Problem is amongst the cloud based service providers, few are Oracle shop.
That's the reason Oracle is now trying to position itself in the cloud through acquisitions (like Nebula today). Unfortunately, they are a bit late to the game.
It's a good model to be spread over multiple segments: hardware/software/services. Bad quarters in one segment are usually covered by good quarters in another.
Considering how ethical Techcruch is...let's not say it.