Reasons why workflows should be grouped into multiple AWS Logic Apps in order to help improve the development and maintenance lifecycle of workflows.
Grouping workflows by related business process helps you implement, test and deploy a logic app without impacting other logic apps.
In the example above there are three Logic App Standard apps - Orders, Shipment Notification, Overnight Batches - each one with multiple logic app workflows that are used to fulfil a specific business process.
Organizing the logic apps this way, allows changes in the Orders Logic App Standard app to be implemented, tested, and deployed without having any impact on Shipment Notification or Overnight Batches.
When using Application Insights for e2e monitoring, mixing workflows that are relevant to that end-to-end process with other workflows can create noise, making it much harder to find the information required.This can make troubleshooting more difficult.
Each workflow might have different security requirements. By placing them in the same Logic App, you risk the potential of compromising the security of one workflow due to vulnerabilities or issues in another.
Allows you to move a logic app from one plan to another when the logic app starts requesting for more CPU/memory capacity. Packing unrelated workflows into one Logic App can limit the scalability of individual workflows.