Azure Data Factory is a cloud-based data integration service provided by Microsoft Azure that enables users to create, schedule, and orchestrate data workflows to move and transform data from various sources to various destinations.

Welcome to the third part of this series of blog posts on How to throw custom exceptions inside Logic Apps. In this series of five blogs, I will cover throwing custom exceptions in Logic Apps. I will cover the following topics: In this third approach, we are going to do a considerable fine-tuning of the previous approach, keeping the same capability to define custom error messages but redesigning the business logic in order to minimize the number of actions and optimize performance.

In the last post, we addressed validating whether a string was null or empty. Today I will speak about another good Best practice, Tips, and Tricks that you must consider while designing your business processes (Logic Apps) and another usual validation requirement: How to validate if an Array is empty or not.

At Lumigo, we heavily depend on a set of tests to deploy code changes fast. For every pull request opened, we bootstrap our whole application backend and run a set of async parallel checks mimicking users’ use cases. We call them integration tests. These integration tests are how we ensure: Recently, we changed our old “traditional log traversing” of integration tests into *amazing* OpenTelemetry traces graphs.

Azure App Service is a platform as a service (PaaS) offering from Microsoft Azure that allows developers to quickly build, deploy, and scale web apps and APIs on Azure. Azure App Service is designed to be highly scalable, allowing you to easily scale your application to meet changing traffic demands. One of its most important features is auto-scaling, which allows your application to automatically adjust the number of instances it’s running based on changes in traffic or demand.

Today I will speak about another useful Best practice, Tips, and Tricks that you must consider while designing your business processes (Logic Apps): How to check if a parameter or a string is Null or Empty.

Azure Logic Apps is a cloud-based service provided by Microsoft Azure that allows users to create and run automated workflows. A trigger is the first step of a workflow that specifies the condition for running further steps in that workflow. Azure Logic Apps creates a workflow run each time the trigger fires successfully. The details of each run, including the status, inputs, and outputs of each step of the workflow instance, can be accessed in the run history section of the Logic App.

As developers we understand the critical role teamwork and collaboration play in solving complex problems. Often, it’s that second set of eyes that uncovers an additional issue or sheds light on the root cause of a stubborn bug. Effective collaboration becomes a critical factor in determining a team’s success or failure, especially when debugging or troubleshooting problematic issues within complex applications.

This article will focus on the metrics side of Azure Functions and features offered by the Azure Portal and then talk about the value of Serverless360. Then about the product that provides beyond the primary feature set in the Azure Portal, which will help you improve the day-to-day operations of your Azure solution. There are many different ways you can manage and operate Azure Functions and features like Application Insights which can also help you with Azure Functions.

This post is part of an ongoing series about troubleshooting common issues with microservice-based applications. Read the previous one on intermittent failure. Queues are an essential component of many applications, enabling asynchronous processing of tasks and messages. However, queues can become a bottleneck if they don’t drain fast enough, causing delays, increasing costs, and reducing the overall reliability of the system.