Azure Database for PostgreSQL Reviews

I am an administrator and infrastructure guy, using PostgreSQL as our database for various applications like ControlM and some homegrown applications. It's used internally for other teams.

PostgreSQL was chosen because it can reside locally on the same server, removing the need to involve a database team. It is also self-maintained, which is a significant advantage. We use PostgreSQL to speed up application development. Our applications are ready sooner because we don't need to depend on other database teams.

PostgreSQL is extremely easy to use and does not require a deep understanding of databases to manage.

There aren't any notable areas for improvement that I could see. PostgreSQL was self-sufficient with no need for additional database knowledge to maintain it.

I have used PostgreSQL for years.

The stability of PostgreSQL posed no problem. Latency was not an issue due to the local deployment.

We were able to scale workloads without significant problems.

The initial setup was straightforward as PostgreSQL was installed locally with no need for migration.

The implementation was done by our team without involving external teams.

We've reduced our total ownership cost because we are not spending on expensive SQL server licenses. I also don't need to purchase licenses for the other teams because I can do it myself. 

I like PostgreSQL's pay-as-you-go pricing because I only pay for what I use. However, it depends on the use case. If the application is in high demand, I'd rather go for a fixed license. I'm using it sparsely, I prefer pay-as-you-go.

I rate Azure Database for PostgreSQL 10 out of 10. It's a great product that does not require you to be a DB admin to manage successfully.

I use it as a relational database in a couple of our products as the back-end relational solution.

Backups are easy, resizing is quick, and the query analyzers help me find out what's happening in each of the queries. Those are the good features.

Support can certainly get better. I have had mixed experiences a lot of times. About 18 months ago, I had a fairly troublesome time with support. After raising multiple escalations, I think it has gotten a little better.

I have used it for maybe five years.

It is pretty stable.

Resizing and other tasks are easy.

Support at best is a five out of ten.

Neutral

The initial setup is straightforward.

We use software to provision. We do not provision from the console. Basically, we fire a pipeline and get it done.

The ROI aspect is fine. I don't see any issue there.

The rating would probably be a seven out of ten. I am not a reseller for Azure. One of our other group companies is. 

We are using Microsoft Azure Database for PostgreSQL as a backend solution and middleware. We utilize it for API gateway solutions, hosting solutions, database solutions, and security solutions. 

Additionally, we are using it as part of our AI solutions.

The operational efficiency of Azure Database for PostgreSQL is good. The cost and benefits ratio is affordable for us. We also use OpenAI services, and everything is affordable for us. We use PostgreSQL for our backend solutions, and security and hosting solutions. 

Overall, we are satisfied with Microsoft solutions and recommend them.

In the future, I would like to see anomaly detection. Currently, when I encounter errors with business rules, I want to know about them quickly. For example, receiving an email when a rule occurs in the database would be beneficial. I am using another solution for this.

I have been using Azure Database for PostgreSQL for five years.

Azure Database for PostgreSQL is stable, and I do not face any issues with it.

I have my own guide, so I do not face any issues with technical support for PostgreSQL.

Neutral

I am not using Cosmos DB. I switched to using PostgreSQL.

Pricing is affordable for us. PostgreSQL is good and affordable for our needs.

From one to ten, I would rate Azure Database for PostgreSQL ten out of ten. However, I am not technical, so my perspective may be limited.