-
|
We implement caching and save the results returned by the GitHub API to avoid over-fetching. When users incorporate our README stats into their README files, it can result in a significant number of fetch requests. According to the GitHub documentation, GitHub Apps are limited to 12,500 requests per hour. By using caching and saving the results, we can efficiently manage these requests and stay within the rate limits. When you want to test the source code on your-side, you can avoid the code that uses Supabase. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
One of the reasons we decided to use Supabase is that we deploy our webpage to a serverless environment on Vercel. As stated in the Vercel Documentation, using Supabase eliminates the need to manage a connection pool or VPC, which saves a significant amount of time. This is especially beneficial for us since we can focus on building and deploying our web application without worrying about infrastructure management. |
Beta Was this translation helpful? Give feedback.
One of the reasons we decided to use Supabase is that we deploy our webpage to a serverless environment on Vercel. As stated in the Vercel Documentation, using Supabase eliminates the need to manage a connection pool or VPC, which saves a significant amount of time. This is especially beneficial for us since we can focus on building and deploying our web application without worrying about infrastructure management.