# Ignition Event Streams thread allocation and backend behaviour

**URL:** <https://forum.inductiveautomation.com/t/ignition-event-streams-thread-allocation-and-backend-behaviour/112855>\
**Category:** Ignition\
**Tags:** scripting, ignition83\
**Created:** [December 17, 2025, 6:16am UTC](https://forum.inductiveautomation.com/t/ignition-event-streams-thread-allocation-and-backend-behaviour/112855 "2025-12-17T06:16:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dean\_So](https://avatars.discourse-cdn.com/v4/letter/d/46a35a/32.png) [@Dean\_So](https://forum.inductiveautomation.com/u/Dean_So)\
**Post date:** [December 17, 2025, 6:16am UTC](https://forum.inductiveautomation.com/t/ignition-event-streams-thread-allocation-and-backend-behaviour/112855/1 "2025-12-17T06:16:51Z")

</div>

I’ve been exploring different solutions for event-based, queued script tasks and have tried out different ways like @pturmel’s suggestion to use java.util.concurrent.LinkedBlockingQueue.

I’m exploring using the new 8.3 module Event Streams as a more native solution and was wondering if there was any information/anyone has done testing on the backend behaviour of these streams? Are they allocated threads on demand as needed? Is it per batch/per stream?

I’m aware it’s early days also but is there any implementation recommendations/best practice when working Event Streams?