# Thoughts on implementing redundancy and high availability flow vs application

**URL:** <https://discourse.nodered.org/t/thoughts-on-implementing-redundancy-and-high-availability-flow-vs-application/98056>\
**Category:** Industrial\
**Created:** [9 July 2025 17:18 UTC](https://discourse.nodered.org/t/thoughts-on-implementing-redundancy-and-high-availability-flow-vs-application/98056 "2025-07-09T17:18:33Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![vitormnm](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/vitormnm/32/52166_2.png) [@vitormnm](https://discourse.nodered.org/u/vitormnm)\
**Post date:** [9 July 2025 17:18 UTC](https://discourse.nodered.org/t/thoughts-on-implementing-redundancy-and-high-availability-flow-vs-application/98056/1 "2025-07-09T17:18:33Z")

</div>

I was thinking about a typical industrial data collection application that requires redundancy.  
It would be better to simply create an application where, if one server fails, the other server just starts a new Node-RED instance with the same project, rather than having to modify files and handle redundancy within the flows. For example, using a heartbeat via UDP with Windows Server.  
Has anyone done something similar?

---

<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:** [9 July 2025 17:27 UTC](https://discourse.nodered.org/t/thoughts-on-implementing-redundancy-and-high-availability-flow-vs-application/98056/2 "2025-07-09T17:27:24Z")

</div>

Shameless Product plug

If you use FlowFuse, you have access to high availability option.

> **[High Availability mode • FlowFuse](https://flowfuse.com/docs/user/high-availability/#:~:text=High%20Availability%20mode%20allows%20you,FlowFuse%20Cloud)**
>
> FlowFuse is the industrial application platform that empowers teams to build, deploy and manage applications that optimize industrial operations.

---

<div class="post-metadata">

**Author:** ![vitormnm](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/vitormnm/32/52166_2.png) [@vitormnm](https://discourse.nodered.org/u/vitormnm)\
**Post date:** [9 July 2025 17:38 UTC](https://discourse.nodered.org/t/thoughts-on-implementing-redundancy-and-high-availability-flow-vs-application/98056/3 "2025-07-09T17:38:02Z")

</div>

Thanks for the link! I wish all my clients used FlowFuse, but I'm still stuck with the old offline Windows setup haha. Still, I see that the way forward is to make the entire application redundant.

---

<div class="post-metadata">

**Author:** ![AllanOricil](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/allanoricil/32/106911_2.png) [@AllanOricil](https://discourse.nodered.org/u/AllanOricil)\
**Post date:** [9 July 2025 17:43 UTC](https://discourse.nodered.org/t/thoughts-on-implementing-redundancy-and-high-availability-flow-vs-application/98056/4 "2025-07-09T17:43:34Z")

</div>

- create a docker image with your flow and node-red
- deploy your image to aws ecs (1 task def and 1 service def with many replicas and rules) + ALB (application load balancer)

all good

Whenever your flow changes, put your service in maintenance mode, then add a task revision with the new container and redeploy the service

Flowfuse is better if you dont want to manage an AWS account, and other infra resources you may need, like a db. They also have a bunch of other cool features.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [9 July 2025 19:41 UTC](https://discourse.nodered.org/t/thoughts-on-implementing-redundancy-and-high-availability-flow-vs-application/98056/5 "2025-07-09T19:41:21Z")

</div>

Don't forget the disclaimer: "Other cloud services are available". 😃

A containerised version managed through a high-availability Kubernetees or similar container orchestrator would indeed likely be a relatively straight-forward way to go.

---

<div class="post-metadata">

**Author:** ![vitormnm](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/vitormnm/32/52166_2.png) [@vitormnm](https://discourse.nodered.org/u/vitormnm)\
**Post date:** [9 July 2025 19:48 UTC](https://discourse.nodered.org/t/thoughts-on-implementing-redundancy-and-high-availability-flow-vs-application/98056/6 "2025-07-09T19:48:33Z")

</div>

Unfortunately I still depend 100% on Windows, a Powershell script seems to be the quickest way to solve this in the Windows environment

---

<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:** [7 September 2025 19:49 UTC](https://discourse.nodered.org/t/thoughts-on-implementing-redundancy-and-high-availability-flow-vs-application/98056/7 "2025-09-07T19:49:27Z")

</div>

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