Plugin + Azure Function + Service Bus: async integration at scale
The article discusses an architecture for asynchronous integration using Azure Service Bus and plugins. It highlights the importance of independent consumers for reliability and scalability in production environments. Key design decisions include message size optimization and correlation ID usage for efficient cross-system tracing.
- ▪The plugin's sole function is to publish messages to Azure Service Bus, allowing independent consumers to handle their respective tasks.
- ▪Each consumer can retry and manage failures independently, preventing issues in one system from affecting others.
- ▪The architecture employs a Topic for multiple subscribers, with subscription-level filtering and dead-lettering to enhance reliability.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3948393) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } SapotaCorp Posted on May 24 • Originally published at sapotacorp.vn on May 24 Plugin + Azure Function + Service Bus: async integration at scale #powerplatform A Dataverse row changes. Five downstream systems need to know: an ERP that tracks financials, a search service that indexes the record, a Power BI dataset that feeds executive dashboards, a notification queue that messages field reps on mobile, and a data lake for analytics retention.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
