GitHub user hanishi edited a discussion: Pekko Ad Network(promovolve)
I’m currently working on a publisher-centric, context-based ad network built on Apache Pekko Cluster. The project is still in active development, but it is intended to be fully open source. I plan to disclose architectural details and share the repository once it is ready. Promovolve is meant to show what Akka/Pekko can actually build when it’s used as a runtime rather than just a convenient toolkit. A lot of systems that moved away after the license change could do so because actors were mainly used as a threading or batch-execution model. That usage was never “wrong”because Akka was explicitly positioned as a toolkit, and partial adoption was always valid. But that part is also the easiest to replace. What tends to be overlooked is the value of the full cluster model. When you commit to this you can build an entire production system with one coherent set of ideas, without stitching together a large collection of unrelated frameworks. Promovolve is intentionally built that way. It’s a complete ad-serving runtime that relies primarily on cluster semantics. The point isn’t that other approaches are wrong, but that the cluster model already gives you all of that, if you let it. Used this way, Akka/Pekko isn’t just a convenience layer, but most simple examples fail to show this, because they stop at actors as a concurrency tool and never reach the cluster semantics where that architectural value actually appears. I felt that going beyond examples and building something fully production-ready would attract practitioners, and that real usage would naturally bring in stakeholders later, thereby increasing Pekko's visibility. While ad tech can be seen as niche, it’s where I’ve spent most of my career, and it’s a domain with a clear path to real revenue. ## Adaptive Budget Pacing with PI Control Demonstrating ad budget pacing that works across all traffic levels https://www.youtube.com/watch?v=Q1kC2slvRec ``` The Setup: Simulated "day" = 300 seconds (5 minutes) Daily budget = $30 (3 campaigns × $10 each) Goal: Spend budget evenly over the day, not too fast, not too slow The Solution: PI controller directly adjusts throttle probability Grace period: Learn traffic patterns before making adjustments Budget cap as safety net Results: Low traffic (64 req/sec): 96% budget delivery, smooth pacing High traffic (380 req/sec): 94% budget delivery, smooth pacing No budget blowouts, stable throughout ``` GitHub link: https://github.com/apache/pekko/discussions/2608 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
