SShortSingh.
Back to feed

Node.js Feature Flag Rollouts: Stable Bucketing for 10% Notification Releases

0
·1 views

Short answer: store the rollout percentage in the flag system, but make the release decision in the request path with a deterministic hash of an immutable user or account ID. For a property-management notification service, that means the same tenant stays on the same delivery path while a 10% release is evaluated; otherwise, users switch cohorts between requests and the delivery-failure signal becomes noise. The least complex useful design is one percentage, one documented hash rule, and one SLO guardrail. Do not call a random-number generator on every request. Do not start with an experiment

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

I Deleted a Kubernetes Pod on Purpose — Here's What Actually Happened

If you're learning Kubernetes, here's a question you should be able to answer: What happens when a production Pod suddenly disappears? Not theoretically. Let's actually think through it. Imagine your application has: 3 Pods ↓ frontend frontend frontend Then someone runs: kubectl delete pod frontend-7d8f9c6d-x82lm The Pod disappears. Your first reaction might be: "Oh no!

0
ProgrammingDEV Community ·

Find an Open-Source Issue Nobody Has Claimed Yet

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 1: Touch Grass Finding a good first issue on GitHub is easy. Finding one that is actually unassigned, relevant to your skills, and worth contributing to is much harder. I built Hacktoberfest Starter to help developers find open-source issues that are actually available to work on. You add your skills and proficiency levels, and the app searches for relevant issues, filters out issues that appear to be already claimed or unsuitable, and helps you identify the issues that are a good match. The goal is simple: spend less tim

0
ProgrammingDEV Community ·

29,151,855 Matches on Port 5060: The Signalling Layer Nobody Maps

29,151,855 Matches on Port 5060: The Signalling Layer Nobody Maps Session Initiation Protocol is how voice and video calls are set up, and port 5060 is where that signalling lives. A ZoomEye query for port="5060" returned 29,151,855 matches, and at that size the question worth asking is what the number actually contains. The query port="5060" was executed on 25 September 2026 with sub_type=all and pagesize 1. The result was 29,151,855 total matches. As before, the number is a match total rather than a sample of live call servers.

Node.js Feature Flag Rollouts: Stable Bucketing for 10% Notification Releases · ShortSingh