> Intermittent network errors
I'm curious about where you're seeing these errors - is this your database functions or "Edge Functions" (Deno)?
Off topic but I am curious:
Why re-deployed unchanged code?
The user-land solution I can think of is cached builds that only re-deploy changed code?
Once you get past a certain amount of endpoints, I'd always want to declare my endpoints in code rather than be tied to their config.
Never had an issue with the logs. Requests still show up.
First thing I always do is read the quotas/limits on any google cloud product before I use it.
Then, I'd notice the increase in deployment times on my CI server as more functions were being added and inspect what was taking so long and try to optimize it. Those individual endpoints take a while to deploy...
We recently tried Supabase on a "frontier" project, and found that it wasn't quite mature enough for production use in our case. Intermittent network errors and lack of an up-to-date status page hampered productivity a bit. These API changes seem like steps in the right direction.
[0] https://firebase.google.com/docs/functions/quotas