# General Query : Subflows vs. Link Call - Roadmap

**URL:** https://discourse.nodered.org/t/general-query-subflows-vs-link-call-roadmap/69788
**Category:** General
**Created:** [30 October 2022 10:29 UTC](https://discourse.nodered.org/t/general-query-subflows-vs-link-call-roadmap/69788 "2022-10-30T10:29:38Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![SandeepA](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sandeepa/32/63225_2.png) [@SandeepA](https://discourse.nodered.org/u/SandeepA)
#### Post date: [30 October 2022 10:29 UTC](https://discourse.nodered.org/t/general-query-subflows-vs-link-call-roadmap/69788/1 "2022-10-30T10:29:38Z")

</div>

Hi ,

I have a general query - How does NR team see the roadmap / future of subflows vs. Link Call.

The main merit of Subflows which i see is -

1. Parameterization - parameters allow on subflow definition - even if static.
2. Modularization (with Link Call - this is fairly achieved).
3. Delivery as Out of Box node (SubFlow as a node).
4. Hopefully - in future - black box delivery - where creation of subflow to node is seamless. And end-user had zero visibility of sublfow's internal implementation.

The biggest advantage of Link Call

1. Modularization
2. Easy Import/Export. (Subflows import/export brings new instance of original flows itself).

Maybe there are more benefits of each - which i am missing.  
I do use both of these and see merits.

Does the NR team - foresee the 2 functionalities meeting in future ?

---

<div class="post-metadata">

### Author: ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)
#### Post date: [30 October 2022 10:46 UTC](https://discourse.nodered.org/t/general-query-subflows-vs-link-call-roadmap/69788/2 "2022-10-30T10:46:02Z")

</div>

> [@SandeepA](#):
>
> The biggest advantage of Link Call
> 
> 1. Modularization
> 2. Easy Import/Export. (Subflows import/export brings new instance of original flows itself).

1. [Singleton](https://en.wikipedia.org/wiki/Singleton_pattern) pattern (one instance)
2. [Polymorphism](https://en.wikipedia.org/wiki/Polymorphism_(computer_science)) (via dynamic message routing)

---

<div class="post-metadata">

### Author: ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [30 October 2022 11:02 UTC](https://discourse.nodered.org/t/general-query-subflows-vs-link-call-roadmap/69788/3 "2022-10-30T11:02:14Z")

</div>

> [@SandeepA](#):
>
> foresee the 2 functionalities meeting in future ?

The link call is an enhancement to the link node - and as you have noted has different characteristics from the subflow node concept - so I'm not aware of any plans to merge them.

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [30 October 2022 11:03 UTC](https://discourse.nodered.org/t/general-query-subflows-vs-link-call-roadmap/69788/4 "2022-10-30T11:03:00Z")

</div>

Further to Steve's comment, the big difference is that with Link Call there is only one instance of the called flow. With Subflows each time you place the subflow on a flow that creates a new instance of the subflow. So, for example, each instance has it's own flow context and if you save context in a function then that is unique to that instance of the subflow.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)
#### Post date: [29 December 2022 11:03 UTC](https://discourse.nodered.org/t/general-query-subflows-vs-link-call-roadmap/69788/5 "2022-12-29T11:03:19Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
