There are threads involved, of course (e.g., there are several workers dedicated exclusively for writing the data into the channel), but you do not occupy any thread for the whole duration of an operation if it's executed asynchronously. In other words, you do not need a separate thread for each operation.
About async IO in general read here: https://en.wikipedia.org/wiki/Non-blocking_I/O_(Java) For implementation in Ignite refer to TcpCommunicationSpi source code. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/How-Asynchronous-support-works-underneath-60-N-put-calls-every-second-tp6482p6813.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
