I am considering the possibility of using Actors in the system to transfer some storage (maybe a database, maybe an assembly in memory). The reason I want to do this is because I do not want calls to the repository to be blocked from the code that calls it, and I intend to push a large amount of messages.
Can an incoming message queue process hundreds of thousands of messages? What is the difference in performance between the code directly calling the method on the object and placing the actor with the queue in the middle?
Greetings
Joe
- dequeue, . . , , OutOfMemoryError.
. , , .. , , , , , . , - , , , .
Source: https://habr.com/ru/post/1716593/More articles:IIS 7, classic application pool, 100% CPU usage issue - iis-7How to determine if filters in a sheet have changed? - filterC compiler flag to ignore sign - cFlash CS3 + AS 3.0 ะัะบะปััะธัั ะทะฒัะบ ะธ ะฒะบะปััะธัั ะทะฒัะบ - actionscript-3Tutorials on creating and deploying a simple java portlet in pluto 2.0 - javause of different delegates - c #Learning how to use irony for .net - c #Minimal client that supports message-level security over the channel interface - wcfCakePHP and .htaccess in a co-hosting environment - cakephpSharePoint list UpdateListItems not updating - c #All Articles