Hey everyone! I'm a Windows/M365 admin, and as I've been transitioning to Azure and utilizing Azure Container Apps, I've been really impressed with the power of containerization. Right now, I'm running SFTPGO in a container that connects to a PostgreSQL database and a storage solution for FTP data. While these Azure components have built-in redundancy, I'm considering setting up a similar on-premises environment and I'm curious about the best practices for redundancy and failover. Should every part of my setup, including VMs, databases, and containers, be designed with high availability in mind? For instance, if I want to maintain systems without downtime during updates, would I need a load balancer for my PostgreSQL database and other components?
1 Answer
Containers really simplify running processes independently on a server. If you're setting up PostgreSQL for your on-prem setup, you definitely want to plan for redundancy just like you would if you were directly installing it on a VM. This means having multiple VMs running PostgreSQL to ensure reliability.
I get that! It seems like containerization is effective in reducing management overhead too. If you design your PostgreSQL in a high availability way with a load balancer, you can avoid downtime caused by updating a single VM. It really does seem worth it to set it up for HA.