PostgreSQL for yesterday AND today's data requirements
Overall Satisfaction with PostgreSQL
PostgreSQL is currently at the core of everything we do. For our organization we knew that we needed a durable, feature rich and flexible database. We have various storage needs including traditional relational setups with auditing for our quoting and invoicing. Inherited structures for project standards that can adapt as needed. And dynamic JSON based data for unstructured data. With PostgreSQL there hasn't been a data problem we have not been able to solve. It allows us to collect flexible data and migrate it into structured data sets that can be utilized with traditional tooling.
Pros
- Runs on a variety of platforms with constant performance and features
- Data integrity is guaranteed
- Wide support for tooling
- Expert advise from core developers is easy to get
- Cloud support through RDS is stellar
Cons
- Many see PostgreSQL as slow or old
- Horizontal scaling not easy
- No column re-ordering
- Speed
- Agility
- Stability
- Redundancy
- Connectivity
- Very low cost of ownership with zero license fees
- Cost of running PostgreSQL using RDS can be high but has lots of value
Much more mature and stable when compared to MySQL with features such as MVCC, complex subquery plans, ORDBMS, and NoSQL support. With Oracle retaining rights to MySQL its future as an open database is less secure and is no longer in the hands of the community. PostgreSQL also excels in extra large dataset handling while requiring lower hardware requirements vs MySQL.
Do you think PostgreSQL delivers good value for the price?
Yes
Are you happy with PostgreSQL's feature set?
Yes
Did PostgreSQL live up to sales and marketing promises?
Yes
Did implementation of PostgreSQL go as expected?
Yes
Would you buy PostgreSQL again?
Yes
Comments
Please log in to join the conversation