Last year, there was a post about moving to Heroku from firebase as firebase mandated credit card even for the free tier. Also, that post explained the issues in giving credit cards for freemium services.
Good bye Firebase and welcome Heroku for free server side execution
As far as I am concerned, the main usage of this free server-side execution mechanism is to host a YouTube API proxy that will be giving data about my YouTube videos.
Why API proxy? My Jamstack Hugo-based personal website (https://joymononline.in) is showing the list of recent youtube videos in my channels. As part of building the site, it makes a call to this API proxy where the API keys and throttling details are hidden.
The YouTube-proxy-API is coded in Node.JS so it can ideally be hosted anywhere supporting the Node.JS execution environment. Normally Node.JS is one of the first technology any hosting platform will support.
Problem
Alternatives
Render.com
https://youtube-proxy-api.onrender.com/api/channels/UC78wYrq_keVaDV8STReHRxg/videos
My Awesome freemium serverless cloud list will be updated later with the features of render to compare with other services.
I am not part of render.com and not affiliated with them in any way. It is an independent post about the experience with render.com
This is just a basic experience. This doesn't mean all scenarios will be easy as hosting a simple API.
No comments:
Post a Comment