Operations | Monitoring | ITSM | DevOps | Cloud

Today I’m going to speak about another important Best practice, Tips and Tricks that you need to take into consideration while you are designing and maintaining your business processes (Logic Apps): Protect your Logic Apps.

The critical use case for BAM is to provide a simplified business-friendly view of the integrated processes that are key to your business. In business today, Robotic Process Automation (RPA) is a trending technology. While it has been around for quite a long time, it has gained a significant boost in popularity alongside the popularity of citizen developer and maker use cases.

Today I’m going to speak about another important Best practice, Tips and Tricks that you need to take into consideration while you are designing your business processes (Logic Apps): Foreach Parallelism.

In the fast-growing Azure space, it is essential to scale your business as Azure scales up. Azure is cost efficient by providing a pay-as-you-go model, but it is still necessary for enterprise users to undergo a Cost Analysis to keep their budget at stack. Let us consider a scenario, you’re a manager in your organization, and your team has been using Azure for the last several months. It has created multiple resources that cost money.

From our experience handling Azure Service Bus messages, one frequent suggestion we get from the support person is to download messages from Azure Service Bus entities like Queues and Topic Subscriptions. By downloading the messages as a local copy, it becomes easy for them to debug the messages and use it at a later point in time. Basic knowledge of Azure Service Bus messaging entities is a pre-requisite for the better understanding of this feature.

Due to the increasing influence of businesses on APIs, the volume of APIs on which they rely, and the administrative challenges that APIs pose, API administration has gained popularity. For the most part, other apps don’t have the exact requirements or construction and management processes as APIs. Vital documentation, higher security standards, extensive testing, frequent versioning, and excellent reliability are all requirements for using APIs properly.

Suppose you are a user of the Microsoft integration stack, and your organization also uses SAP. In that case, you will likely have use cases where an IDOC triggers integration processes in SAP being published. One of the good things about Logic Apps on Azure is that a connector for SAP allows you to register to receive IDOCS published by SAP, and you can then use them in your integration processes.