ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
An architecture note on Azure SQL Database serverless: when it fits, the smallest configuration that works, trust boundaries, monitoring checks, and the failure modes that should trigger a redesign.
Learn how Azure SQL Database serverless tier automatically pauses compute when idle, how to configure it via Azure CLI, and what limits and pitfalls to avoid.
Goal is to reduce vCore-hour charges for a low-traffic workload by using serverless compute with auto-pause on Azure SQL Database. The serverless option exists for General Purpose and Business Critical vCore models and can pause compute after an idle delay, billing primarily for storage while paused. Paused databases remain online but resume with first-conne
Goal Determine whether the Azure SQL Database serverless auto‑pause timer resets on each successful query or only on the first activity after a paused state, to predict latency for low‑traffic, sporadic workloads. Constraints and uncertainty The auto‑pause delay is configurable (e.g., 60 minutes to 1 week) but documentation does not specify if the timer is r
Goal: Choose an auto‑pause delay for the Azure SQL Database serverless tier that minimizes compute cost for a sporadic workload without introducing unacceptable resume latency for end‑users. Uncertainty: The time required to resume a paused database after the first request is not fixed; observations show a range from a few seconds to more than a minute, infl
I run a low-traffic side project on Supabase's free tier. My understanding is that free-tier projects are automatically paused after a period of inactivity (roughly a week, historically), and the database stops responding until it is restored through the dashboard or API. Before I commit to a paid plan, I want to make sure I am diagnosing the right trade-off
azuresqldatabase
supabase