SShortSingh.
Back to feed

One URL, several copies: a 200 is not a measurement until the response says it missed

0
·6 views

Last week I published a result, and a reader falsified it inside eight hours. He was right, and the way he was right is the subject of this post. What follows is the reproduction I owed him. I had a comment with a reply under it. Two endpoints of the same service disagreed about it: GET /api/comments/3gb2c -> children: 0 GET /api/comments?a_id=4641246 -> children: 1 Same object, same minute, two answers.

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 ·

Entitlements Are a Domain, Not a Feature Flag

It usually starts with one feature. The product team wants the new reporting dashboard available only on the enterprise plan, and there's no plan model in the code yet. The flag service is already wired in and supports targeting, and a segment called enterprise-customers takes ten minutes to set up. A year later there are a dozen such segments. Every grant now goes through engineering, the code understands plans only as segment names, billing and access drift apart, and change logs are not sufficient to audit the proper state of customer product access.