Render of Heroku Battle Royale

Original link: https://editor.leonh.space/2022/render/

Today is the third day of my run from Heroku :p, and also the third day of the daily update of this small station. Today, I want to introduce you to the 23rd district of Tokyo, Japan… Wrong frequency…, today To know Render, it is also a PaaS service. The previous Koyeb always felt that it was not stupid enough, and only supported GitHub, and the status indication during the period from construction to deployment was not in place. Let’s see if Render can satisfy the picky ones. I am!

In terms of foolishness, Render seems to be very confident. Steps 1-2-3 are emphasized below the front page of the homepage:

Render 1-2-3

The actual feeling is also the same. The screen when creating a new platform is simpler. Feed it a GitLab / GitHub project, and it can recognize that the language of the project is Python. The package is installed with pip, and almost only the platform name needs to be filled in. :

Render - New web service

You can also see the machine specifications and amounts of each Render solution in the picture. The Starter costs $7 per month, and the CPU only has half a CPU. Sure enough, there is nothing perfect in the world.

Looking back at the Free solution, the CPU only says “shared”. In fact, it is unknown how powerful the garlic grains are, but Render is the same as Heroku, which will put the service to sleep, and the Render time is more stringent, and no one uses it for 15 minutes. Hibernation, that unspeakable CPU garlic granule, just from personal experience, it takes longer to wake up than Heroku, it seems that it can only be used for toys!

This article is reprinted from: https://editor.leonh.space/2022/render/
This site is for inclusion only, and the copyright belongs to the original author.

Leave a Comment