There are (for GCP anyway, no experience with other serverless providers) pay-as-you-go models for certain components that scale down to 0. That allow you to keep a little-used project running for minimal expense.
E.g., on GCP: App Engine Standard + Datastore.
Yep, my emoji-compress.com is on an appengine like that.
Is not serverless, is just a container and you still have to think of provisioning when u make the config.
Serverless like functions or lambdas are also a good option for event-driven flows.
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
There are (for GCP anyway, no experience with other serverless providers) pay-as-you-go models for certain components that scale down to 0. That allow you to keep a little-used project running for minimal expense.
E.g., on GCP: App Engine Standard + Datastore.
Yep, my emoji-compress.com is on an appengine like that.
Is not serverless, is just a container and you still have to think of provisioning when u make the config.
Serverless like functions or lambdas are also a good option for event-driven flows.