Stitcher Engineering Blog offers insights, tutorials, and updates on building scalable, reliable, and high-performance systems for podcasting and audio streaming. Covering topics such as backend architecture, media processing, and content delivery, Stitcher Engineering Blog provides resources for developers and engineers working in the audio streaming industry. Developers can learn about building resilient systems, optimizing media workflows, and delivering high-quality audio experiences through Stitcher's blog posts and technical articles.

stitcher.io

A developer optimized their blog's analytics system to process 11 million events, improving performance from 30 to 14,000 events per second through systematic changes: removing unnecessary database sorting, reversing nested loops, ditching the ORM for raw queries, replacing closures with while loops, fixing framework serialization overhead, and using indexed ID-based pagination instead of offsets. The rebuild time dropped from 50 hours to 10 minutes per projector.

Processing 11 million rows in minutes instead of hours

<pre><code class="language-php"> // Loop over each projector 
foreach ($projectors as $projector) {
 // Loop over each event
 foreach ($storedEvents as $storedEvent) {
 // …
 }
 }
</code></pre>
Although i skim read this, but each time i see nested loop i always wondered is there a way to remove the other loop if each event can be processed to multiple projector why not using concurrency or parallelism (well it’s php but still)? just a thought.

Intersting article, I digged more into event sourcing after this. Thanks.