Learn How To Fortify Your SaaS

-- Optimized Rate Limiting Configuration CREATE TABLE IF NOT EXISTS rate_limits ( user_id INT PRIMARY KEY, req_count INT DEFAULT 0, last_req TIMESTAMP ); -- Efficient Rate Limit Checker CREATE OR REPLACE FUNCTION check_rate_limit( p_user_id INT, p_max INT, p_window INT ) RETURNS BOOLEAN AS $$ DECLARE v_now TIMESTAMP := CLOCK_TIMESTAMP(); v_last TIMESTAMP; v_count INT; BEGIN SELECT req_count, last_req INTO v_count, v_last FROM rate_limits WHERE user_id = p_user_id FOR UPDATE SKIP LOCKED; IF v_last IS NULL OR v_now - v_last > make_interval(secs := p_window) THEN UPSERT INTO rate_limits (user_id, req_count, last_req) VALUES (p_user_id, 1, v_now) ON CONFLICT (user_id) DO UPDATE SET req_count = 1, last_req = v_now; RETURN TRUE; ELSIF v_count < p_max THEN UPDATE rate_limits SET req_count = req_count + 1, last_req = v_now WHERE user_id = p_user_id; RETURN TRUE; END IF; RETURN FALSE; -- Rate limit exceeded END; $$ LANGUAGE plpgsql; -- Quick Test SELECT check_rate_limit(42, 100, 60) AS proceed;