![]() ![]() The simplest top-level way to think about the question: “which Postgres service on Azure is right for my application?” is this: That’s what I call the “2 elephants in the room.” Choice is good, but it begs the question: how do you choose? On Azure, we have two different managed services you can choose from for Postgres. Which has the benefit of letting somebody else deal with the hardware and operating system, configure high availability, architect for security, manage the backups, and make sure the updates happen. Why a managed Postgres service? Primarily so you can outsource your database operations and focus on your application. You can of course install and self-manage Postgres on an Azure VM.īut most of you who run your apps in the cloud do so on a managed database service. And when you decide to run your application in the cloud on Azure, you have a few choices. Many of you choose Postgres when selecting a database for your application. Choice of 2 Azure managed services for PostgreSQL ![]() Of course, it takes a village: for many of the open source bullets in the diagram above, our contributions were not made in isolation-and involved collaboration from developers and community members across the Postgres community, and from other companies, too.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |