4 ms·
Why Hyperic is Going to Support PostgreSQL Only As a Backend Database
- elchief 14y agoGrammar Nazi Rises: "Why Hyperic is Going to Support Only PostgreSQL As a Backend Database"
- acchow 14y agoNothing nazi about this. The title is semantically different from what was intended.
- ulysses 14y agoSo Hyperic started with PostgreSQL, added MySQL and Oracle, dropped PostgreSQL, and now have dropped MySQL and Oracle and have gone back to PostgreSQL. Why would I go with a product that's going to require me to change the backend database every few years?
- stusmall 14y agoI never really got the reason why the switched back to PostgreSQL. It kind of read like "I was told to do this and it ended up being way less painful than I thought it would be". In the end it doesn't sound like they really gained that much either.
- benjarrell 14y agoI think the switch back is because VMware has their own (relatively new) customized PostgreSQL (vPostgres http://www.vmware.com/products/application-platform/vfabric-postgres/overview.html http://www.vmware.com/products/application-platform/vfabric-...) that they sell/support.
- vFabricTeam 14y agoIt's a reasonable question to ask why you should trust us given several changes in the past, however considering this move makes Hyperic invested in a VMware supported database, I think the likelihood of it changing again any time soon is dramatically lower. Also, since this is a "eating your own dogfood" kind of move, I would actually deem this a very good thing for the product in the long term for scalability and general performance.