I'm actually quite amassed that some developers are completely oblivious to the underpinnings of how their software works. Some of them really do feel source code runs on water vapour!
If you are genuinely having a break down because Heroku will stop being free and you haven't figured out that there are absolutely hundreds of other ways to achieve the "serverless feel"--which is basically near free as well, then there is no more hope left for humanity!
- App and all backend APIs scale to zero (Cloud Run is hosted Knative)
- PHP WebSocket server used by the chat application (single instance of PHP CLI maintains app state) with a chatbot that is integrated into Google Dialogflow
- Zero-cost asynchronous worker runs for the lifespan of the running WebSocket server container
- Server-side rendering implemented using Symfony Twig
- MVC without the M (clear separation of concern/backend components)
- RequireJS implemented on the frontend
- CV integrated into the Request Interview API that ships as a microservice
If you are genuinely having a break down because Heroku will stop being free and you haven't figured out that there are absolutely hundreds of other ways to achieve the "serverless feel"--which is basically near free as well, then there is no more hope left for humanity!