Tag: integration

Background Jobs in Heroku with Azure Service Bus

Jan 14, 2021 · 11 min read

Web applications are optimized for throughput and latency to service a high number of HTTP requests as quickly as possible. For improved performance, web applications defer the CPU intensive, IO intensive, time-intensive, and scheduled processing workloads to background jobs that run independently of the user interface. These background jobs must function without intervention from the user interface and should not block a synchronous user and system interaction. Offloading slow and compute or memory-intensive activity to background jobs improves web applications' performance and throughput.

#azure#integration#heroku

Read more of Background Jobs in Heroku with Azure Service Bus

Implementing Multi Session Sequential Convoy Pattern with Azure Service Bus and Go

Jan 02, 2021 · 10 min read

In many event-driven applications, preserving the sequence of events is essential. For example, an event-driven eCommerce application might have the following states, transitions, and events. A user adds N items to the basket. This action generates the item added event. The user checks out the basket. This action generates the basket checked out event. The user pays for the items. This action generates the payment made event. Inventory decrements the count of available items by N.

#azure#integration#programming

Read more of Implementing Multi Session Sequential Convoy Pattern with Azure Service Bus and Go

Lab: Tip or Code sample Lab: Tip/Code sample No Code Incident Management System with Azure Logic Apps

Sep 06, 2020 · 8 min read

In this lab, we will create an Azure Logic App that monitors Twitter, analyzes the sentiment of customer tweets with Text Analytics v2 service, and creates incidents in Pager Duty. PagerDuty is an incident management platform that provides reliable notifications, automatic escalations, on-call scheduling, and other functionality to help teams detect and fix problems quickly. This application can help customer service agents react swiftly to customer complaints and avoid brand reputation damages.

#azure#integration

Read more of No Code Incident Management System with Azure Logic Apps

Building and Testing Reactive Microservices in Azure with Event Grid, Azure Functions, and Ngrok

Apr 12, 2018 · 10 min read

According to the Reactive Manifesto, a reactive system should have some essential characteristics which include: responsiveness, resiliency, elasticity, and being message-driven. Out of all the aspects, the most significant differentiating factor of Reactive Microservices from others is its characteristic of being message-driven. Using messages as the glue that holds your Microservices application together, you can design systems that isolated. High degree of isolation also helps enhance the scalability of a system which is an essential aspect of a Microservices application.

#azure#integration

Read more of Building and Testing Reactive Microservices in Azure with Event Grid, Azure Functions, and Ngrok