Co-author - Bijoy Valsan
Let's take a look at how the Flow Run plan operates with IBM App Connect Enterprise as a Service. With this plan, customers using IBM App Connect Enterprise as a Service on AWS can efficiently purchase a specific number of invocations for their Integration flows. In this blog, we will explore the advantages of the Flow Run plan over the VPC plan and provide guidance on deploying a Designer flow or Toolkit BAR file using the Flow Run plan.
VPC vs Flow Run
|
Resource Unit (Flow Run) Plan
|
Charged based on hours used
|
Charged based on the number of invocations of your flows
|
Manage the integration runtime and deployments
|
Manage only the deployments
|
Better cost efficiencies at larger scales
|
Affordable pricing, ideal for small to medium-sized businesses
|
Usage may be more challenging to predict without experience
|
Streamlined sizing estimation and straightforward execution model
|
Deep expertise required for effective management
|
Simplified forecasting and entitlement tracking
|
For detailed examples of what counts as an invocation, see Pricing plans in the App Connect Enterprise as a Service documentation.
Now, let’s explore an example of how to deploy an integration with our new plan.
How to deploy a flow on the Flow Run plan
I have an upcoming event published in Eventbrite. I need to get the list of people who registered for my event daily as a Slack message. I have created an Event-driven flow using the Eventbrite and Slack connectors to achieve this.