Event Throttling
No enterprise application works in isolation, as they all have dependencies of some kind. They have to work with other applications in the enterprise ecosystem to add value to organizational processes. These applications can be built using completely different technology stacks and they might have been developed in different programming languages and they might support data in different formats. If we need to communicate with these systems, we might need to define some sort of enterprise messaging framework. A common approach for this is messaging through a database or messaging system (MSMQ, NServiceBus, and so on). In a client-server application developed using Microsoft's APIs, we might use sockets for messaging, or other techniques such as named pipes. The most modern of all in our times is message queuing. It is based on the publisher/subscriber model. There are different message queuing systems available in the market. Microsoft also has its own product, called MSMQ...
