ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Integration boundary PM2's zero-downtime reload mechanism relies on sending SIGUSR2 to the master process, which then forwards SIGTERM to workers for graceful shutdown. The application must implement a SIGTERM handler that finishes in-flight requests before exiting. This contract sits at the boundary between PM2's process orchestration and the Node.js runtim
I have microk8s v1.22.2 running on Ubuntu 20.04.3 LTS. Output from /etc/hosts : 127.0.0.1 localhost 127.0.1.1 main Excerpt from microk8s status : addons: enabled: dashboard # The Kubernetes dashboard ha-cluster # Configure high availability on the current node ingress # Ingress controller for external access metrics-server # K8s Metrics Server for API access
Implementing least-privilege access in Azure SQL Database often involves utilizing Microsoft Entra ID Managed Identities to remove hardcoded credentials. In this architecture, the application relies on OAuth2 tokens that possess a finite lifespan and must be refreshed to maintain a persistent connection to the database engine. A challenge arises when the ide
MATLAB Production Server (MPS) supports hot-deployment, allowing updated compiled archives to be uploaded without restarting the server instance. This mechanism enables zero-downtime updates by routing requests to the newest available version while existing workers complete their current tasks. A potential constraint arises during the transition period when
Compare suitability, operational responsibilities and limits before choosing this technology for a project. Which trade-offs should guide the decision?
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
Goal: Assess whether enabling the automatic repository archiving feature (introduced in Bitbucket Cloud 8.12) will lower storage expenses for repositories with infrequent activity while preserving required read‑only access. Archived repositories become read‑only, blocking pushes, pull requests and Pipelines execution. Storage is billed at a reduced rate, but
NixOS maintains system immutability by storing configurations in the /nix/store . While system generations are atomic and easily reversible, stateful data—such as database directories, log files, or persistent user configurations—typically reside outside the immutable store to survive transitions. A challenge arises when using nix-collect-garbage to prune ol
The goal is to determine whether the New Relic Java agent records the exact moment a HikariCP connection pool reaches its maximum size, or only reports aggregated connection counts at each harvest window. The agent collects pool metrics on a default 60‑second harvest cycle, and Java agent 8.x renamed the metric namespace from Database/ConnectionPool/* to Dat
pm2
nodejs
kubernetes
matlab
cloudflare
bitbucket
nixos
newrelic