Architecture

 

i-Stream's server architecture is based on a multi-threaded asynchronous I/O design to provide blistering performance while supporting thousands of concurrent requests simultaneously.

 

Instead of a traditional thread-per-session architecture that starves precious server resources as the number of connections (and threads) increases, i-Stream leverages multiple worker thread pools to respond to communication, application, and timing events asynchronously.

 

Developing software around asynchronous designs can be daunting and complex. To simplify the transition for developers without compromising server performance, i-Stream employs a "plug-in" protocol architecture that insulates the internal thread management, messaging, and timing layers from the application design, and provides enhanced protocol functions that mirror many of the blocking concepts that developers are accustomed to using.

 

i-Stream's server core also provides enhanced port and transport management to allow connected clients (or "sessions") to operate within the same virtual server instance, even when communicating over different transports or ports. This allows, for example, collaboration applications to centrally control messaging, access, presence monitoring, and permissions even when clients are connecting over TCP, PDP, and UDP simultaneously, and into different server ports in order to bypass local firewall restrictions.