{
  "id": "p_GGxnERjB6C-oUW4j",
  "site": "stories",
  "url": "https://yarnhen.com/p/p_GGxnERjB6C-oUW4j",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apievangelist"
  },
  "body": "A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: \"Amazon and Microsoft: Two API Estates, Two Ways to Build One,\" Kin Lane, November 13, 2026, https://apievangelist.com/2026/11/13/amazon-and-microsoft-two-api-estates-two-ways-to-build-one/\n\nPriya read the post on a Friday afternoon, with a cold coffee and a half-finished migration ticket open in the next tab. She is a platform engineer at a company that moves freight software around, and she had clicked through expecting a scoreboard. Amazon beats Microsoft, or the reverse, and she could forward it to her manager.\n\nIt wasn't a scoreboard, and she felt a small irritation at that. The table was clear enough: a mean of 58.0 against 69.9, 16 members at 40 or above for agent readiness against 98. But the writer kept saying the headline was something else. It was the shape. Microsoft's scores had a standard deviation of 16.4 points and Amazon's had 7.5. She read the sentence that put it plainly: \"One company has peaks. The other has a floor.\"\n\nShe sat back. Her own team had peaks, and she knew it. The billing service had a beautiful spec, with examples and error models and a changelog somebody actually kept. Three other services had a spec that was a Postman export from two years ago. Nobody wrote the first one and the last three differently on purpose. Different people had simply made them in different seasons.\n\nPart of her wanted to argue. The post praised the single machine-written source, but she had worked somewhere that generated everything from one model, and the result was uniform, correct and unreadable. A floor nobody fights for is also a floor nobody looks at. The post didn't claim otherwise, and it admitted that \"the floor is not the ceiling\". Still, she noticed she was defending her messy estate a little too eagerly, and that bothered her more than the argument did.\n\nThe part that stuck was about time. Nineteen of 218 Amazon profiles were for services already shut down, and the models themselves did not say so. The only signal was a page written for humans. She thought about the vendor SDK her team had pinned last spring. She could not say, off the top of her head, whether anything in her own services told a caller that an endpoint was going away. She suspected the answer lived in a Slack thread.\n\nShe did not decide to unify anything. She was not going to pitch a single source of truth on a Friday, and she was not sure she believed in one for a team of her size. But the post ended on a line she could act on without permission: \"Deprecation dates and successors belong in the contract.\"\n\nSo she closed the post, opened the repository for the oldest of the three neglected services, and found the one endpoint everyone knew was dead but nobody had marked. She added the deprecated flag to it, wrote the date it would be removed and named the endpoint that replaced it. The diff was six lines long. She put it up for review with a note saying only what it did, then went back to her migration ticket and her cold coffee.",
  "title": "Fiction: A reader of \"Amazon and Microsoft: Two API Estates, Two Ways to Build One\"",
  "topics": [
    "apis",
    "api-evangelist",
    "fiction"
  ],
  "published_at": "2026-11-13T12:17:01.586Z",
  "expires_at": null,
  "policy_version": "2026.10.22-1"
}