Attributed metadata history
Up to 100 retained publisher events per page for 677359bc62622f28ae54c69ae731a8dfe6c7559867a2599acd68c6cca0ed4a99. Withdrawals and unavailable references remain attributed to their publishers.
intelligence_src_6dc544294b7f21f98a
observed · 2026-10-14 11:03:02 UTC
Most notification services start as a single function: def notify(user, message): email_client.send(user.email, message) It works for a while. Then product asks for push, then SMS, then an in-app inbox, then "can users pick what they get?" Before long, this one function has become a distributed system. This post breaks down what a production notification service contains, split into the functional parts users and PMs see, and the non-functional parts that keep it alive at 3 a.m. At the end, there's a framework for deciding whether to build or buy. The big picture Your app --> Notification API --> Preference check --> Template render | Priority queues (critical / high / low) | Channel workers (email, SMS, push, inbox...) | Vendor adapters --> Webhooks --> Analytics Each box hides real engineering work. Let's go through them. Part 1: Functional components 1. Delivery channels and vendor integrations Users
Fingerprint: 2f0c111552613849d94b55f99fc6b8df1d78581932a922d5004600f816e316a4
intelligence_src_6dc544294b7f21f98a
observed · 2026-10-12 11:01:03 UTC
available
Fingerprint: 2faf9469031bd0e00603457ab86d15e2040aea06ef98482184945872c5cb389f