dyno | simple dynamodb client | AWS library

I have a react application (Node back end) running on Heroku (free option) connecting to a MongoDB running on Atlas (also free option). When I connect the application from my local machine to the Atlas DB all is fine and data retrieved (all 108 K records) in about 10 seconds, smaller amounts (4-500 records) of data in much less time. The same request from the application running on Heroku to the Atlas DB fails. The application running on Heroku can retrieve a small number of records (1-10) from the same collection of (108 K records), in less than a second. As soon as I try to retrieve a couple of hundred records the system fails. Below are the logs. I included the section of the logs that show a successful retrieval of 1 record and then failing on the request for about 450 records.

I have three questions:

1. What is the cause of the issue?
2. Is there a work around in the free option of Heroku?
3. If there is no work around in the free option, what Heroku pay level will I need to get to and what steps will I need to take to get this working? I will probably upgrade in the future but want to prove all is working before going in that direction.

Logs:

Build is successdul and it is producing application error, i have set up host name and debug=False as suggested but it is still causing error in opening the browser window, i am new to heroku so please suggest what needs to be done to make it work

my settings.py

I am trying to deploy my first ever application, which has django for the backend and react for the frontend (with create-react-app). I followed the steps in some tutorials and managed to get my deploy build running but I am getting an error for npm start. I can't seem to find any solution, any help will be more than welcomed.

Have an issue running react-scripts build on a heroku-20 nodejs dyno

Heroku runs npm start which is

I have a Node.js app running a React front-end hosted on Heroku which is linked to a Github repository so that on push it redeploys the app. I have been using the app this way without problem for around a year now.

It works on Heroku Local, and running the node app locally without Heroku but I'm getting a 503 service unavailable error when I run a put request when running the app online.

2021-06-01T08:04:27.326913+00:00 heroku[router]: at=error code=H12 desc="Request timeout" method=PUT path="/api/auth/login" host=myapp.herokuapp.com request_id=9b84f5c5-def4-4dce-82d2-baf1bef3a9a8 fwd="90.215.204.78" dyno=web.1 connect=1ms service=30000ms status=503 bytes=0 protocol=https

Any pointers?

I am using Heroku for deploy, mongoDB Atlas as Database and Strapi as Headless CMS. Heroku is already working with hobby Dyno. Yesterday I added some data into my database with some pictures and it was working fine but after 24 hours my Strapi doesn't display the pictures, I checked my DB and seems like I still have documents with photos. So if you encountered this problem before where is the problem and how did you sol it?

I deployed my Node.js WebApp to heroku but I'm getting this error

I have a Docker container which I'm trying to deploy as a Heroku application. My application is called

Intro

I am currently running a Spring-Boot application through Heroku on a single web dyno. Due to the large number of intensive background tasks (fetching resources from 3rd party APIs, sending mails, etc.), I would like to move all these "heavy jobs" on a second worker dyno/process. However, I am facing several difficulties in properly exposing the application components (e.g. @Repositories) to the second worker process.

What I have attempted so far

I've created a second main class (BackgroundWorker) which I specify in the Procfile as a worker process. The following class is then called in order to initialize the background tasks.