What is your primary use case for Azure Database for PostgreSQL?

My main use cases for Azure Database for PostgreSQL are to use it as data storage for a lot of apps, involving different app services, functions, and other platforms, where we bring in and process a lot of data for integrating different cloud platforms. We have document management systems where we're pulling back-end data from on-premises systems or other cloud systems, using many Azure functions and different app services to pull data through Azure Database for PostgreSQL to track and sync with other systems.

My main use cases for Azure Database for PostgreSQL came from a personal project to scratch an itch, and it was the easiest one to go grab. I appreciate how easy PostgreSQL is to get running locally. You can grab a container and run it, as opposed to the old days when having a local database was very challenging and required special scripts that would take hours to run. Now I can grab a container and be good to go in seconds, which makes life a lot simpler and has influenced my application development process.

As an infrastructure platform engineer, I deploy and administer the databases to be used with our security apps as well as some customer-facing applications. Since I do not do any development, the integration of Azure Database for PostgreSQL with other services impacts our application development by focusing on AI, and we utilize Copilot for everything and anything we can to secure and support our customers. I assess the impact of automatic patching and backups on my database management strategy by noting that they have saved us time; anything automatic is a blessing. It allows us to be hands-off, and the reliability has been very good with it. We are in the process of expanding usage by migrating off of MySQL to PostgreSQL for several security applications, and it is going very well; once the database is up and we have all our scheduled jobs or tasks in place, it pretty much runs hands-off.

Our main use cases for Azure Database for PostgreSQL are straight up database with the extra support for the JSONB functionality. We have some DocumentDB options out there and some Cosmos as well. Having the best of both worlds with the relational data, but then you can append the schemaless data kind of along for the ride is our main use case. It's mostly structured data, but with the support for the unstructured data that's a first-class citizen, not just a string column in a database.

My main use cases for Azure Database for PostgreSQL are application support, mostly integration with applications. Azure Database for PostgreSQL has been able to influence my application development process or my customer's application development processes by knowing that at least the forecasted performance you will get out of the database, it becomes a top choice. When thinking about it from a business requirement perspective and forecasting or estimating the tools you want to implement, it comes to mind because of the out-of-the-box experience around performance.

For the last four years, we have been a huge customer of Azure Database for PostgreSQL. We migrated from a single machine to Flex Server and are now evaluating the elastic capabilities. We are from American Airlines, so we do a lot of price optimization and network optimization. We use Azure Database for PostgreSQL for price optimization and network optimization. This involves large-scale data, which we have traditionally used Oracle Exadata database for in our systems today. When we migrated to Azure, PostgreSQL proved to be very beneficial and performed on par with what Exadata can do.

We have a few custom-built applications where we use Azure Database for PostgreSQL as the database layer. It is not used for Azure Database for PostgreSQL because it's for an online service.

My main use cases for Azure Database for PostgreSQL are Edge, Edge AI, and edge data consolidation.

Azure Database for PostgreSQL is included in our SaaS solution. It is one of the components of the SaaS solution built by us. Azure Database for PostgreSQL is deployed for all our customers, making it a key component for us. All our Microsoft users are using this solution, so it is a key one.

My primary use case for Azure Database for PostgreSQL is migrating our traditional SQL 2012 into PostgreSQL purely for cost savings.

Although I don't use Azure Database for PostgreSQL every day, I often review the security side of it whenever there is a new requirement because I'm a security engineer, and I make sure that the particular service is appropriate for our environment. I have been using it for three years.I particularly don't use the features of Azure Database for PostgreSQL; I just create it, make sure everything is secured, and ensure it's secure as per our environment. But I'm not physically going there and using it. I just use it to make sure the particular PostgreSQL is secure, and I appreciate the navigation and documentation. Whenever I'm using a new product, I look for the documentation because I want to know what's going on. With PostgreSQL, the documentation is perfect, and using it on Microsoft is easy because there is documentation for Microsoft PostgreSQL, which I find easy to follow. My experience with the monitoring and management tools provided by Azure Database for PostgreSQL involves sending all the logs to Azure Sentinel; we enable diagnostic settings and send our logs to Azure Sentinel. We prefer managing all our logs related to any tool, whether it's on-premises or cloud-based, then we use syslog to send it to Sentinel. We enable diagnostic settings on every service, and we have policies to auto-enable the diagnostic settings, and all the logs go to Sentinel. Meanwhile, we filter some of the unwanted logs, such as audit logs, which we don't need all of. Azure Database for PostgreSQL definitely influences our application development process, especially since we have a team of developers who are continuously trying to play with the latest products and keep up with what's going on with our competitors. We use this database, and not just PostgreSQL; we also try multiple other databases provided by Azure, but so far, PostgreSQL has been easy. I don't want to name them, but we have tried other databases; however, there is a learning curve. Instead of trying to teach a developer or a person on learning that, since PostgreSQL has been around for a while, most of our developers prefer using it.

Currently, for Azure Database for PostgreSQL, we are seeing that many of our customers in the education and nonprofit sectors are looking for a more easily consumable way to work with their data. When you consider those two industries, they are not about high spend, but about maximizing credits and consumption when it comes to being able to compartmentalize and publicize data. Azure Database for PostgreSQL is a foundation before any type of thoughts could even be considered in the AI space.

We are an insurance company with many applications that handle policy processing, so we use Azure Database for PostgreSQL for those applications. We have different usage for every database, and for all of our in-house applications, we use Azure Database for PostgreSQL.

Our main use cases for Azure Database for PostgreSQL include security dates, security tools, and a couple of small applications that move data and read data from other sources such as logs or claims and process it. Some of our use cases are simple websites that use Azure Database for PostgreSQL. We are starting with Copilot and agents built from Copilot. It will almost be the year of our agent for next year because many people are asking for Copilot Studio. On the keynote, we saw the old App Maker or App Builder. I am always looking at how people can make small things and be out the door already using the Azure Copilot environment. We are looking forward to that.

We started using Azure Database for PostgreSQL ( /products/azure-database-for-postgresql-reviews ) about five to six years ago. Initially, we were doing an on-premises Kubernetes ( /products/kubernetes-reviews ) setup, but since Azure ( /products/microsoft-azure-reviews ) was accepted at the bank, we moved to Azure ( /products/microsoft-azure-reviews ). We currently run fairly large clusters with around five clusters spanning three environments, along with disaster recovery aspects and smaller clusters for specific products.

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

Our primary use cases of PostgreSQL are migrations for our customers. We specialize in Oracle to Postgres migrations. We offer customers the potential advantages and cost savings of migrating to Postgres.

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.

At a prior agency, we used the solution primarily for reporting, incident situation awareness, and providing public information regarding different safety programs. It's used for general information sharing within the public domain, and it is nothing too complicated or in-depth.

We have turned on pgvector, which is an extension for the vector search. We use PostgreSQL as the RAG database for the Gen AI application.

We're a managed service provider using Azure Database for PostgreSQL to deliver services to 300 customers, so there are potentially 300 different use cases. We use it as a normal database instead of MySQL or Azure SQL because PostgreSQL performs well, especially with the flexible server. We do many things in the cloud with Kubernetes containers, and our customers can use a containerized version of Postgres. We abstract it so that it runs in Azure itself instead of being part of the Kubernetes cluster. It makes sense to go from Postgres to Postgres.