Slashdot Mirror


Open Source Databases "50% Cheaper"

pete314 writes, "Open source databases can cut the total cost of ownership of a database by up to 60% compared to the cost of running proprietary databases from Oracle, Microsoft or IBM. According to data collected by Forrester Research, the savings average about 50%. Open source databases however still struggle to reach mission-critical enterprise applications because enterprises perceive them to be less secure and stable."

8 of 276 comments (clear)

  1. enterprises also want by rubycodez · · Score: 5, Insightful

    enterprises also want paralleling clusters and failover clusters. The open source databases are getting there, give it few more years.

    1. Re:enterprises also want by wiggles · · Score: 4, Insightful

      The one place that the Open Source products have a long way to go is support. Companies don't think mysql and postgres are unreliable, they're just not backed enough. The company I work for could give a rat's hindquarters about TCO -- they just want to outsource their risk so that if something breaks, the CIO/CEO/Chairman has someone to argue with. The Chairman can play golf with Larry Ellison as he tries to get more concessions out of Oracle, but he can't play WOW with the 19 year old kid who added some bit of code to mysql.

      And before you say it, MySQL AG is still small potatoes compared to Oracle, Microsoft, or IBM.

  2. 0% savings for me by Crudely_Indecent · · Score: 5, Insightful

    For those of us who can't afford to run a commercial database package, and have been running open source databases from the beginning, this isn't news. MySQL and Postgres are your friends.

    --


    "Lame" - Galaxar
    1. Re:0% savings for me by glwtta · · Score: 4, Insightful

      Open Source Databases are only free if you don't value your time.

      Dude, have you actually used both Postgres and Oracle? There is not an entity on this earth less respectful of my time than Oracle (well, maybe ClearCase) - the thing is an absolute nightmare to administer. Sure, it needs the complexity because of its advanced scaling capabilities; but most of us are not amazon.com, and never will be.

      On the other hand, the administrative overhead of running Postgres is damn near 0% (MySQL is a different story entirely of course).

      Sure we are a small company, and only have under a TB of data in our databases, but there are a lot of companies in the same position who shell out ridiculous amounts of money for Oracle (only for the name-brand, nothing else), and then someone ends up stabbing themselves in the eye in frustration (might be a slight exaggeration). Or else pay for a full time DBA; I've worked for a company with 3 developers and 1 full time Oracle DBA - that's just nuts.

      --
      sic transit gloria mundi
  3. Re:This just in! by rossifer · · Score: 4, Interesting
    This just in, 0 is less than 100!

    Seriously did someone really need to do a whole study to determine this and then write an article telling the world?
    If you need clustering, failover, remote backup, separation of indices from data, you make heavy use of materialized views, and you need to retrain your DBA's on a new database, there are a lot of people who still say that it will cost you more to use Postgres than Oracle. Don't even think about MySQL.

    But if you're starting from scratch on a new project and your current projections don't indicate you'll need a lot of those features, now the PHB's will have finally heard that free databases should be considered. We deployed on SQL Server and Oracle after developing on Postgres (because Postgres was about twice as fast when running the test suite). Postgres scaled better than Oracle on any single box configuration, and customer data sets never required more than 100GB databases in the worst case.

    We were forced to deploy on Oracle and SQL Server because none of our customers thought that Postgres was enterprise qualified. Now, some of them might.

    Regards,
    Ross
  4. your mileage may vary by kpharmer · · Score: 4, Interesting

    This is a pretty trivial article which seems driven by ingres.

    Anyhow, a few things that I'd consider:

    1. since as the author mentions the open source databases aren't ideal for mission critical applications (yet), then many organizations will find themselves supporting multiple databases. Say, oracle for financials & crm & the corporate warehouse and postgresql for a variety of smaller projects. Makes sense in many ways - except: oracle is already free for the small databases anyway, and now you need the dbas to support multiple products. This is going to increase your labor costs - not decrease it.

    2. for many large analytical databases (data warehouses, etc) the cost of using open source are actually higher than closed source. This is because db2, oracle, etc are better at using the hardware than the open source alternatives. They've got better optimizers, parallelism, far better partitioning, better better pool management, automatic query rewrite, etc. So, a $100k oracle lisense running on a $100-200k 4-way (i know, assumes discount) will out-perform postgresql (free) on a 16-way ($1m) in many ways.

    3. for some applications mysql could be more expensive than oracle. Ok, not just because you need to do far more testing with mysql to make sure that none of the wacky silent errors are affecting your code. But also because of the odd licensing - that requires its own faq and tips to just license the product if you can't figure it out. Then there's enterprise db - not very familiar with this one, but I doubt that it is free. Meanwhile, at the low-end the big-three database vendors all support free products. So, whether or not you pay more may very well depend on how you use the software.

    Of course, if you're at a company like mine, and get to bypass purchasing and just review the license & install - you probably are saving a vast amount of money after all.

  5. product support is over-rated by kpharmer · · Score: 4, Insightful

    > People are far more dependable when they're working for money than for charity.

    not when they suck - which they frequently do when working on product support teams.

    yes, I'm glad that I'm working with supported products - but I also avoid calling them like the plague. It is very much a worst-case scenario.

  6. Where are the test results? by msobkow · · Score: 4, Insightful

    Do you seriously think any CIO with a functioning brain cell is going to go with free unsupported software when they can't even find a single reference to such databases from any certified performance evaluation companies or organizations?

    The downtime cost of one single failure in a five year period for a mission critical system can easily run 100 times the cost of a commercial product with support. Only bean counting fools risk their entire business without properly assessed risks and disaster recovery plans.

    Not having someone to source the recovery of the smouldering crater that was your data center is a huge issue.

    --
    I do not fail; I succeed at finding out what does not work.