The Hub Pattern: Keeping Supabase Edge Functions Under 50

The Hub Pattern: Keeping Supabase Edge Functions Under 50 Supabase Edge Functions have an implicit constraint: there's a practical limit to how many you should deploy. In my project, I've made this explicit as the [EF-CAP-50] rule: 50 functions maximum, enforced by CI . The pattern that makes this possible is the hub pattern . The Problem: EF Count Creeps Up Early in the project, I followed the natural path of one-feature-one-EF: check-competitor-updates get-competitor-features update-competitor