Publisher — Subscriber Pattern with Azure
We can see in most of the modern applications consists of many modules and those modules requires lot of integrations among those to make the application to complete a business flow. Ex : In an event management system when a new event is registered , that registration module needs to notify the Venue Handling, Speaker Management and ticketing modules. It is very important that we keep publisher and the subscribers decoupled so we can introduce new modules (new features) to the system without changing the existing systems. Also modern systems requires high scalability we need to make sure publisher and subscriber integration happens asynchronously with out waiting. Publisher- subscriber model is one of the most commonly used pattern to solve the above business problem. When is comes azure there are many options for us to select as message broker, each of them seems quite similar to each other but each has its own strengths and weaknesses. Let’s first see what the messaging/ Events ser