ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Cloud & infrastructure · #heroku
Handling Idempotency in Heroku Postgres When deploying applications on Heroku, the Heroku Router may trigger request retries under specific failure conditions. If a request successfully commits a transaction to Heroku Postgres but the response fails to reach the router, a subsequent retry can lead to duplicate data entries. While PostgreSQL supports ACID tra
My Node.js app is able to work with local Postgres database via npm pg module. I can connect to the Heroku hosted Postgres database (free Hobby Dev plan) via command line with heroku pg:psql command as well. But when my Node.js app is trying to query to Heroku hosted Postgres database I am receiving an self signed certificate error. Here is the output with s
Developers expect Heroku Scheduler to trigger jobs according to a local time zone that matches the application’s intended audience, especially after moving the app to a different geographic region. The platform does not automatically adjust the scheduler’s execution time based on the dyno’s region, leaving the timing dependent on the TZ configuration variabl
Goal: Ensure that a Heroku web dyno reliably binds to the $PORT environment variable within the 60‑second boot window to prevent Error R10 (Boot timeout). Constraint: The current platform does not expose a way to adjust the boot timeout or to receive early warnings when the dyno fails to bind $PORT, leaving developers to rely solely on the final R10 log entr
Heroku dynos default to UTC at the operating system level to maintain consistency. While setting the TZ environment variable via application config alters how the runtime interprets relative date-time strings, this configuration is isolated to the dyno environment. There is a potential synchronization discrepancy between the application's local time interpre
We need a pagination strategy for a Heroku‑hosted PostgreSQL table that will grow beyond one million rows and must serve API responses under 200 ms. The two documented approaches are offset pagination (LIMIT/OFFSET) and keyset pagination (WHERE id > last_id using a server‑side cursor). Constraints include Heroku’s default 20‑connection pool, pgBouncer run
Goal Determine whether the Heroku platform provides a built‑in mechanism to assign a regional time zone to individual dynos so that timestamps in platform‑emitted data such as logs, metrics, and scheduler runs reflect that zone instead of UTC. Constraints and uncertainty Heroku dynos run with the system clock set to UTC and the platform does not apply a regi
Goal: determine whether a steady rise in RSS reported by Heroku’s dyno metrics reflects a genuine memory leak in the application or expected platform behavior such as garbage‑collection jitter or undocumented swap usage. Constraints: Heroku exposes only the total memory footprint via ps:info , with no per‑process or heap breakdown; dynos may restart after de
Goal: Determine whether enabling Heroku autoscaling for a low‑traffic application yields lower monthly cost than running a single hobby dyno (with free dyno hours) when the app experiences intermittent requests. Constraints: Free dyno hours provide ≈550 h/month but cause the dyno to sleep after 30 minutes of inactivity, adding latency on wake‑up; autoscaling
javascript