Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
PostgreSQL: A great opensource database
What do you like best about the product?
PostgreSQl is a wonderful piece of software that allows the easy storage, transfer and querying on spatial and non-spatial data. I particularly like, and extensively use, the PostGIS extension for spatial querying and representation with other software, notably QGIS. Its this seamless integration with other open source software that really makes PostgreSQL stand out. Finally, the backup methods through pg_dump are simple to use and ensure you can always take a backup before any major changes.
What do you dislike about the product?
I sometimes find it tricky to use from the command line and prefer using the pgAdmin III GUI for use. This is no fault of PostgreSQL though, merely my own shortcomings with operating databases from the command line.
What problems is the product solving and how is that benefiting you?
We are generating a data marketplace and looking for somewhere to store spatial data and querying this on the fly so we can send back the results to our users. Upon initially using MongoDB it was clear that this solution lacked the geospatial strength we needed so quickly switched to PostGreSQL.
Recommendations to others considering the product:
Go for it - you wont be let down! Its simple to set up, easy to administrate and provides a stable environment for storing and querying large amounts of spatial data
- Leave a Comment |
- Mark review as helpful
My experiences with PostgreSQL
What do you like best about the product?
PostgreSQl is a great piece of open source software that handles the storing, processing and extraction of large spatial and non -spatial datasets incredibly well. I wouldn't hesitate in recommending this piece of software. I particularly like, and regularly use, the PostGIS extension for spatial querying and representation in other software e.g. QGIS. Its the interactivity with other software that makes PostgreSQL stand out. Worth a mention is the backup facility of pg_dump - a quick and simple method to create those vital backups.
What do you dislike about the product?
Not much. I prefer using the GUI pgAdmin to navigate through PostgreSQL but that is not the fault of the software - merely my attachments to GUI's.
What problems is the product solving and how is that benefiting you?
We are building a marketplace that is storing and serving up geospatial data on our front end. This was initially done using MongoDB but its ha snow become apparent that Mongo has some issues with querying geospatial data on a large scale. Given the expertise PostgreSQL has with this - we are now starting to shift all our data holdings over so we can handle geospatial data with ease.
Recommendations to others considering the product:
Go for it - its easy to setup and start testing with data. Add the PostGIS extension to maximise your geospatial data.
All that we need, at an acceptable price
What do you like best about the product?
I like the NoSQL key-value store (HSTORE) that works out of the box and binary JSON storage. This allows me to keep the SQL-based pipeline I have, yet venture into NoSQL land safely. And all of that for free.
What do you dislike about the product?
It had a bit of a learning curve to use properly.
What problems is the product solving and how is that benefiting you?
We are analysing large antibody datasets. Thanks to these analyses multiple vaccines against viral diseases have been developed.
Fairly scalable, easy to configure, easy to maintain
What do you like best about the product?
I like that it is both lightweight and fast. It's pretty lean on resource consumption. Replication is easy to set up and pretty well documented by the Postgres Development Group. I like that it was easy to make changes to replication and access permissions without having to do a full restart of the database. I several times found my self impressed by how resilient the database was. Disk filled up? Add more storage and restart the database without data file corruption (YMMV). Your replication slave broke and you don't have the logs on disk for it to catch up? Blow it away, clone the master, and restart replication (don't use the postgres version in the AWS repo).
What do you dislike about the product?
In comparison to any other database technology that I've worked with, Postgres was easy to work with. "It wasn't implemented correctly", "replication was set up wrong", "the server capacity was misguessed when it was launched:" These are downsides to any technology where there is a general lack of knowledge. There's a simple way to avoid those problems: Hire a DBA, or experienced sysadmin and take their advice. There is problem with a lack of general knowledge when it comes to open source technologies combined with the fact experienced technologists all seem to have their own beloved biases. But those problems are not related to the technologies in use, but rather the people that use them.
Scalability never became an issue, but I haven't seen a lot of solutions for building hot-hot clusters, or putting multiple instances behind a connection manager for horizontal scalability, and trying to research multi node clusters will tell you how to set up synchronous/asynchronous master/slave replication at best or make you realize that a lot of the PG user community does not know the difference between high availability and scalability.
Scalability never became an issue, but I haven't seen a lot of solutions for building hot-hot clusters, or putting multiple instances behind a connection manager for horizontal scalability, and trying to research multi node clusters will tell you how to set up synchronous/asynchronous master/slave replication at best or make you realize that a lot of the PG user community does not know the difference between high availability and scalability.
What problems is the product solving and how is that benefiting you?
Postgres made it easy to create redundant copies of data for both our front end web applications, and back end APIs servers. It allowed us to build applications with a high level of data redundancy in our production environments while simultaneously synchronizing that data to a DR environment. The addition of Postgres support in Amazon RDS was also a good indication of that some of the problems that we faced on standalone instances were quickly and easily solvable (as long as you are not using the Postgres packages available from Amazon, which are missing some key utilities).
Recommendations to others considering the product:
As with anything else try to accurately predict your requirements, and when in doubt supersize. Maybe hire someone with some experience to implement, and maintain it. If you hire an expert, take their advice.
PGSQL
What do you like best about the product?
- Open source and liberal Open Source license
- Big community
- Active development
- Partition, JSON, streaming replication support
- Performance
- Master-Master
- Transaction safe DDLs
- Big community
- Active development
- Partition, JSON, streaming replication support
- Performance
- Master-Master
- Transaction safe DDLs
What do you dislike about the product?
- Master-Master georeplication(BDR) not production ready yet.
- Missing Oracle-like stats reports(has 3rd party tools but not enough)
- Missing administration GUI(like Oracle's enterprise manager)
- Missing Oracle-like stats reports(has 3rd party tools but not enough)
- Missing administration GUI(like Oracle's enterprise manager)
What problems is the product solving and how is that benefiting you?
We are using DB for telco data and have over 40 installations. Huge inserts and huge reports are used over PGSQL. Even default config on limited systems, PGSQL runs fluently and reliably. We also develop software products using PGSQL and without adding extra cost to our customers' bill, we get benefit with lower price.
Postgres
What do you like best about the product?
open source, large community, some nice functions that get updated.
What do you dislike about the product?
parallel queries not available yet.
not as frequent w/ patches or new function releases
not as frequent w/ patches or new function releases
What problems is the product solving and how is that benefiting you?
RDMBS for reporting and meta info storage
Awesome open source database
What do you like best about the product?
I love the large feature set built into Postgres. In particular, range queries are a godsend for time-based applications. Full-text search functionality means I don't have to bother with an elastic search installation. There is also much additional functionality that can be gained via extensions such as postgis.
What do you dislike about the product?
Replication can be a pain to configure compared to other DBs. Hosted solutions like RDS takes care of this though.
What problems is the product solving and how is that benefiting you?
I used Postgres for a scheduling web app. Because range queries are built in, it's a lot less effort to query compared to MySQL. It's also more efficient. I also use the full-text search functionality for our built-in knowledge base, as well as the trgm extension to order search results.
Recommendations to others considering the product:
If regulations require you to encrypt data at rest, Postgres might be problematic. Postgres does not support database level encryption out of the box. Encryption at rest could possibly be achieved via full disk encryption. You can get this on medium sized RDS instances on Amazon. Otherwise, there is an extension for row level encryption.
powerful open-source database option
What do you like best about the product?
PostgreSQL is well-documented, powerful, mature, and has a huge user base. Easy to find examples and forum postings when troubleshooting just about any scenario: the odd error message, problems using pgAdmin, figuring out how to integrate PostgreSQL into your node.js application.
What do you dislike about the product?
For some use-cases, PostgreSQL isn't the best option. It's worth considering your needs and looking at SQLite, MongoDB, and others.
What problems is the product solving and how is that benefiting you?
We needed an open source database for a variety of one-off web apps and dashboards. Postgres does a great job of it.
Simply the best
What do you like best about the product?
I am a huge fan of the robust data types and procedural capabilities in PostgreSQL. I used MySQL for many years simply because the setup process seemed easier than what PostgreSQL required. When PostgreSQL announced support for the JSON data type, I decided to bite the bullet and give PostgreSQL a more serious look. I've not touched MySQL since then.
In the years since JSON support landed in PostgreSQL, I've learned to appreciate the various options for implementing your own functionality using plpgsql and python. I've also experimented with various Foreign Data Wrappers (FDW) to expose data from other sources (filesystem, mysql, redis, other PostgreSQL instances, etc) as tables in PostgreSQL. I'm constantly impressed.
In the years since JSON support landed in PostgreSQL, I've learned to appreciate the various options for implementing your own functionality using plpgsql and python. I've also experimented with various Foreign Data Wrappers (FDW) to expose data from other sources (filesystem, mysql, redis, other PostgreSQL instances, etc) as tables in PostgreSQL. I'm constantly impressed.
What do you dislike about the product?
In today's day and age, redundancy and clustering are very important. Plenty of other databases out there offer relatively simple options for setting up replication, sharding, and automated failover. PostgreSQL doesn't have much built in to address these concerns. There are myriad projects that facilitate these important features, but none of them feel great to me. Perhaps I just need more time to invest in them.
What problems is the product solving and how is that benefiting you?
I've used PostgreSQL for a wide variety of tasks from simple structured data storage to data warehousing to powerful analytics. In every case, I've found PostgreSQL more than capable and quite pleasurable to use for the task at hand.
Recommendations to others considering the product:
Compared to MySQL, PostgreSQL is hands down the better option. More correct behavior when inserting and updating rows. Robust data type options. Long history of being fully open source. Vibrant community.
A solid database with a long track record
What do you like best about the product?
PostgreSQL has a long history as a go-to open source database with a full set of features, an active development and user community, and an accessible and robust toolset. Users of PostgreSQL and its derivatives (Vertica, RedShift) will feel equally at home. The toolset has remained largely compatible since I started using it around 1999.
What do you dislike about the product?
PostgreSQL isn't always the first to adopt new features, or to adapt to new changes in the computing world. This is two-way street: one way it means the platform is stable and its constraints are reasonably well-known, in the other direction it means that PostgreSQL misses out on performance opportunities around multi-core query execution, optimization for the shift of the CPU/RAM/SSD/disk balance, and clustering/failover.
What problems is the product solving and how is that benefiting you?
I have used PostgreSQL in a number of scenarios, including as a backend for MediaWiki, a hand-coded website, a SQL application ported from MySQL, a SQL app ported to Oracle, a Reporting database ported from Oracle, and some data warehouse/analytic tasks.
PostgreSQL performed admirably in each, with the caveat that the more one deviated from the traditional RDBMS with many small transactions, the more work was placed on the developer to optimize their data structures or query strategy to wring the most from the database.
PostgreSQL performed admirably in each, with the caveat that the more one deviated from the traditional RDBMS with many small transactions, the more work was placed on the developer to optimize their data structures or query strategy to wring the most from the database.
Recommendations to others considering the product:
Compare PostgreSQL to other platforms like MySQL, RedShift, Vertica. Decide on whether you want your database to do much of the optimization work for you (Vertica) or need to scale elastically (RedShift). Either way, PostgreSQL is a solid and free starting point that remains largely compatible with its cousins.
showing 561 - 570