Ensure Backend Starts Only If Database is Connected

[Parth06102006]

Currently:

The backend server calls app.listen(...) independently.

Database connection logic is handled separately in a controller/service.

This means the API starts even if the database is down, leading to runtime errors when endpoints are called.

Proposed Change:

Modify the startup flow so that the backend only starts (app.listen) after a successful database connection.

If the database fails to connect, the server should not run, and an error should be logged.

Advantages:

✅ Fail Fast Principle – prevents the server from running in a broken state.

✅ Better Reliability – avoids confusing runtime errors caused by missing DB connections.

✅ Cleaner Error Handling – startup logs clearly show database connection issues.

✅ Consistency – ensures that all APIs depending on the DB will work once the server is running.

Why This Should Be Added:
Right now, the app can misleadingly appear “healthy” (server listening), even if the database is unavailable. This could cause problems in production monitoring, CI/CD pipelines, or health checks. By enforcing database connectivity at startup, we guarantee the app only runs when fully functional.

[Parth06102006]

@Annanyatiwary4 kindly see the issue as I feel it is important for the server to run only if the dbConnetion is established otherwise the issue of error in database connection and server starting may be fatal for the controller t not work due to no connection with datababse