4 ms·

A few key missing features: - You can't write off or expense three martini lunches and golf excursions with a PostgreSQL sales rep. - When you deal with unava

A few key missing features: - You can't write off or expense three martini lunches and golf excursions with a PostgreSQL sales rep. - When you deal with unavailability, you can't point to the PostgreSQL support SLA's four hour response and tell your boss "not our problem". - It's harder to justify larger budgets for your IT fiefdom and thus your sense of self-importance when you don't pay for unnecessary license fees.

dragonwriter 8y ago
> You can't write off or expense three martini lunches and golf excursions with a PostgreSQL sales rep. That's one of the Oracle features supported by EnterpriseDB’s proprietary downstream version. > When you deal with unavailability, you can't point to the PostgreSQL support SLA's four hour response and tell your boss "not our problem". Also, this, but it is a 24 hour resolution window for Severity 1 issues. > It's harder to justify larger budgets for your IT fiefdom and thus your sense of self-importance when you don't pay for unnecessary license fees. EnterpriseDB addresses this, but certainly doesn't usually match Oracle in the budget impact department.
dkhenry 8y ago
So I know your comment is a bit tongue in cheek, but there are real concerns about the last two points that people may not realize. At many large orginizations the outside vendor may be the _only_ real technical capabilities that team has so there is no solution other then "outsourcing" to the vendor's support team. Budgets have similar incentives that make teams want to keep a large budget around even if they could get the job done with less resources. That slush money comes in handy to have the vendor do all sorts of work that isn't really about getting their system running ( i.e. doing all the integration with other parts of your stack ) I think lots of open source products or smaller teams think winning those "Enterprise" deals is about having the better product and checking some boxes on a requirements sheet. When you get into enterprise its all about the relationships
sroussey 8y ago
Sometimes it’s clustering, upgrading servers, replication layouts that work and don’t have random issues with WAL, encryption at rest without requiring the os to do it (has this been fixed?). Maybe having clustered indexes, good partitioning, etc. Still, I’m hard pressed to ever recommend anything other than PostgreSQL or MySQL.
kerng 8y ago
I know your post is sarcastic, but some of these (eg. 2) are real concerns for large enterprises. Enterprises want not just a product but a solution and that includes support and all that comes with it.
- ric2b 8y ago
  You can pay for Postgres support as well.

dragonwriter 8y ago

> You can't write off or expense three martini lunches and golf excursions with a PostgreSQL sales rep. That's one of the Oracle features supported by EnterpriseDB’s proprietary downstream version. > When you deal with unavailability, you can't point to the PostgreSQL support SLA's four hour response and tell your boss "not our problem". Also, this, but it is a 24 hour resolution window for Severity 1 issues. > It's harder to justify larger budgets for your IT fiefdom and thus your sense of self-importance when you don't pay for unnecessary license fees. EnterpriseDB addresses this, but certainly doesn't usually match Oracle in the budget impact department.

dkhenry 8y ago

So I know your comment is a bit tongue in cheek, but there are real concerns about the last two points that people may not realize. At many large orginizations the outside vendor may be the _only_ real technical capabilities that team has so there is no solution other then "outsourcing" to the vendor's support team. Budgets have similar incentives that make teams want to keep a large budget around even if they could get the job done with less resources. That slush money comes in handy to have the vendor do all sorts of work that isn't really about getting their system running ( i.e. doing all the integration with other parts of your stack ) I think lots of open source products or smaller teams think winning those "Enterprise" deals is about having the better product and checking some boxes on a requirements sheet. When you get into enterprise its all about the relationships

sroussey 8y ago

Sometimes it’s clustering, upgrading servers, replication layouts that work and don’t have random issues with WAL, encryption at rest without requiring the os to do it (has this been fixed?). Maybe having clustered indexes, good partitioning, etc. Still, I’m hard pressed to ever recommend anything other than PostgreSQL or MySQL.

kerng 8y ago

I know your post is sarcastic, but some of these (eg. 2) are real concerns for large enterprises. Enterprises want not just a product but a solution and that includes support and all that comes with it.

ric2b 8y ago
You can pay for Postgres support as well.