# Flow with 10 MQTT "IN Node".. is better use just one "IN node" and split via "function node"?

**URL:** <https://discourse.nodered.org/t/flow-with-10-mqtt-in-node-is-better-use-just-one-in-node-and-split-via-function-node/94627>\
**Category:** General\
**Created:** [14 January 2025 20:49 UTC](https://discourse.nodered.org/t/flow-with-10-mqtt-in-node-is-better-use-just-one-in-node-and-split-via-function-node/94627 "2025-01-14T20:49:30Z")\
**Posts on this page:** 1\
**Showing post:** 19

<div class="post-metadata">

**Author:** ![jbudd](https://avatars.discourse-cdn.com/v4/letter/j/5f8ce5/32.png) [@jbudd](https://discourse.nodered.org/u/jbudd)\
**Post date:** [20 January 2025 14:41 UTC](https://discourse.nodered.org/t/flow-with-10-mqtt-in-node-is-better-use-just-one-in-node-and-split-via-function-node/94627/19 "2025-01-20T14:41:38Z")

</div>

> [@Semmu](#):
>
> everything branched out from that one single entry point, making my flows very ugly and messy and hard to follow, manage, etc

I'm a bit surprised you feel your flows are less messy, and easier to maintain, with a seperate config node and mqtt-in for each discrete topic.  
What happens when you change your MQTT password?  
Still, I can see the appeal of a discrete input point for each flow / section of a flow.

> [@Semmu](#):
>
> And it has no "real" performance impact, since it uses 1 MQTT connection (per config node)

[This thread](https://discourse.nodered.org/t/throttle-mqtt-traffic-at-flow-startup/94660/12) illustrates a problem with a particular cloud based broker service and one mqtt-in per topic.

---

_[View the full topic](https://discourse.nodered.org/t/flow-with-10-mqtt-in-node-is-better-use-just-one-in-node-and-split-via-function-node/94627)._