From 1a8d3cc2d520c81f2a01f78abde691d739a6cd0f Mon Sep 17 00:00:00 2001 From: Mubashir Osmani Date: Sat, 23 Aug 2025 16:22:56 -0400 Subject: [PATCH] Added FAQ under deployment docs (#13912) * updated faq questions * updated faq * added faq under deployment --- docs/my-website/docs/proxy/deploy.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/my-website/docs/proxy/deploy.md b/docs/my-website/docs/proxy/deploy.md index 701fc49223..7f89306864 100644 --- a/docs/my-website/docs/proxy/deploy.md +++ b/docs/my-website/docs/proxy/deploy.md @@ -1010,5 +1010,13 @@ User-agent: * Disallow: / ``` +## Deployment FAQ + +**Q: Is Postgres the only supported database, or do you support other ones (like Mongo)?** + +A: We explored MySQL but that was hard to maintain and led to bugs for customers. Currently, PostgreSQL is our primary supported database for production deployments. +**Q: If there is Postgres downtime, how does LiteLLM react? Does it fail-open or is there API downtime?** + +A: You can gracefully handle DB unavailability if it's on your VPC. See our production guide for more details: [Gracefully Handle DB Unavailability](https://docs.litellm.ai/docs/proxy/prod#6-if-running-litellm-on-vpc-gracefully-handle-db-unavailability) \ No newline at end of file