11 ms·
Saying a proprietary database works well with a proprietary operating system is not a feature in the age of IaC and the cloud. I understand there are still loa
by AtlasBarfed 3y ago
Saying a proprietary database works well with a proprietary operating system is not a feature in the age of IaC and the cloud.
I understand there are still loads of enterprises stuck in the windows zone, but ... It's not ideal.
As for query performance, I doubt it id that significant... Well, unless you are constrained by a proprietary db license and approved CPU count / machine size and need to squeeze more from less.
Because if you are on postgres and are bumping into hardware limits, a slightly better query planner is a very short term bandaid.
At that point, you are likely a year past the point where you should take your biggest queries and refactor/architect scale them to dynamo or Cassandra or something like that.
I mean, bragging about active directory integration in 2024. It should be a dumb LDAP / identity provider,not some chain bonding you to Microsoft software in perpetuity.
- briHass 3y agoIt's not necessarily a good choice for cloud, where the DBA-level responsibilities are handled for you, and the per-hour premium doesn't buy you much. SQL Azure is really only a fit for applications/expertise already tied to SQL Server, not something that would be a first choice for greenfield work. However, assuming a non-cloud environment (on-prem), SQL Server Standard on a powerful server can go a very long way for about $7-10K in one-time licensing cost. This also buys you product support, which doesn't exist for free for PG.