Aug 2026· Zenodo (CERN European Organization for Nuclear Research)
Abstract
Multi-tenant Software-as-a-Service (SaaS) platforms rely on webhook change notifications from cloud APIs such as Microsoft Graph to synchronize calendar and resource-booking data in near-real time. Empirical analysis reveals a structural failure in this model, which we term webhook event amplification: a single state mutation triggers a burst of unordered notifications carrying no deduplication token. Controlled measurement shows the provider delivering approximately nine times the notifications the subscription model warrants, reaching a mean of 53 notifications per mutation in the most severe configuration. Left unmitigated, this exhausts downstream compute, degrades observability, and introduces race conditions that compromise transactional idempotency. Because providers offer no native suppression and delta queries target periodic synchronization rather than real-time deduplication, remediation must occur at the subscriber edge. This paper introduces the Distributed Notification Broker (DNB), which interposes a four-stage filtering pipeline between the webhook source and downstream consumers, combining tenant-isolated partition-keyed streaming, delta-validated event propagation, and content-hash business-change detection so that only verified, business-relevant changes propagate. Empirical evaluation over a 78-day observation period demonstrates an 88% reduction in downstream processing volume, a substantial reduction in concurrency-induced race conditions restoring system stability, an 89% reduction in volume-attributable infrastructure cost, and a 68% reduction in total infrastructure cost.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The perception of the impact of agile methods is predominantly positive, and several challenge areas were discovered, but based on this study, agile methods are here to stay.
M. Laanti, O. Salo, P. Abrahamsson· Information and Software Tec...· 260 citations· ⚡20
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 8, 2026
Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity. The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.