Enable PM2 Cluster Mode for Zero‑Downtime Scaling of a Node.js Application
Learn how to run multiple instances of a Node.js app with PM2 in cluster mode, verify the setup, and perform seamless reloads without dropping connections.
Loading…
ReadMeFeed / Community knowledge
#zero-downtime
Real questions. Useful conversations. Find the people who know your stack.
pm2
nodejsAchieving Zero-Downtime Node.js Deploys with PM2 Cluster Mode
Stop dropping requests during deployments. Learn how to use PM2 cluster mode and rolling reloads to achieve zero-downtime updates for Node.js apps.
Keras Model Serving with TensorFlow Serving: Zero‑Downtime Model Update via Version Alias
Goal Deploy a small Keras image‑classification service behind TensorFlow Serving and update the model to a new version without interrupting incoming inference requests. Constraints The serving instance must continue to accept requests during the swap, and the update mechanism should rely only on TensorFlow Serving’s built‑in version‑alias feature rather than
kerasHow can I add a non-null column with a default using Doctrine Migrations without causing downtime?
I need to modify the schema of a small application that must stay online, and I want to use Doctrine Migrations to perform the change. The table contains a moderate amount of data, and I cannot afford a long lock that would block reads or writes. I am unsure which sequence of migration steps—adding the column as nullable, deploying updated code, backfilling
doctrineHow can GitKraken’s branch synchronization be used to migrate a small application to a new environment without downtime?
Our team needs to move a small Node.js application from a legacy server to a container‑based environment while keeping the service continuously available for users. We intend to use GitKraken’s branch synchronization feature to keep a preparation branch in sync with the main branch across repositories, allowing us to test the new deployment setup without aff
gitkrakenHow can I use GoLand's built-in Docker integration to migrate a small Go service to a new container image without downtime?
I have a small Go application currently running in a Docker container managed by GoLand's run/debug configuration. I want to update the container image to a newer base image while keeping the service available during the transition. GoLand provides Docker integration that can build, push, and run containers, but I am unsure how to orchestrate a rolling updat
docker
golandHow can I use Gradle's configuration avoidance API to migrate a small application's build logic without causing downtime during the transition?
Consider a small Java application built with Gradle 8.x that currently uses eager project configuration in its build scripts. The team wants to adopt Gradle's configuration avoidance APIs (such as {@code Provider}, {@code Property}, and lazy task inputs) to improve build performance and enable future enhancements. The application must remain available to use
gradleManaging Hibernate schema migrations during Scalingo rolling updates
Scalingo implements zero-downtime deployments through rolling updates, where new containers are spun up and health-checked before the previous version is terminated. This mechanism ensures continuous traffic flow via the platform's load balancer. When deploying Java applications using Hibernate ORM, there is a potential conflict between the rolling update pr
hibernate
scalingoPM2 Cluster Mode and Database Schema Migration Interoperability
PM2's zero-downtime reload mechanism sequentially restarts process instances in cluster mode to maintain application availability. While this ensures the service remains online, it creates a period where multiple versions of the application code coexist during the transition. When a deployment includes a destructive database schema change, the remaining acti