[{"data":1,"prerenderedAt":79},["ShallowReactive",2],{"blog-\u002Fblog\u002F2024\u002F03\u002Fscaling-node-red-devices-vs-flowfuse-instance":3},{"id":4,"title":5,"body":6,"description":12,"extension":68,"meta":69,"navigation":74,"path":75,"seo":76,"stem":77,"__hash__":78},"blog\u002Fblog\u002F2024\u002F03\u002Fscaling-node-red-devices-vs-flowfuse-instance.md","Scaling Node-RED with FlowFuse: Differences between a FlowFuse Instance and a Device Instance",{"type":7,"value":8,"toc":59},"minimark",[9,13,18,21,25,28,32,45,49,52,56],[10,11,12],"p",{},"FlowFuse is a Software as a Service (SaaS) platform designed to enhance the experience and capabilities of Node-RED for its users. By focusing on scalability, security, and Dev Ops, FlowFuse aims to remove some of the technical barriers associated with using Node-RED, making it easier for citizen developers to automate tasks, process data, and create applications. In this blog post, we will discuss the differences between a FlowFuse instance and a FlowFuse device instance while highlighting how FlowFuse addresses scalability challenges in Node-RED deployments.",[14,15,17],"h2",{"id":16},"scalability-challenges-with-traditional-node-red-deployments","Scalability Challenges with Traditional Node-RED Deployments",[10,19,20],{},"While deploying Node-RED is quite simple, managing multiple instances across different environments can become complex and time-consuming. As the number of devices and use cases grow, users face difficulties in scaling their Node-RED applications efficiently to handle increased load without compromising performance or security. This is where FlowFuse comes into play.",[14,22,24],{"id":23},"the-role-of-flowfuse-as-an-orchestration-tool","The Role of FlowFuse as an Orchestration Tool",[10,26,27],{},"FlowFuse functions as an orchestration tool that allows the deployment and management of all your Node-RED instances at scale, addressing scalability challenges head-on. By leveraging its platform, users can quickly deploy and manage multiple Node-RED instances while ensuring optimal performance and security. This enables them to connect with a wide range of devices, from PLCs and sensors to legacy software, without worrying about the complexities of managing their Node-RED deployment.",[14,29,31],{"id":30},"deploying-node-red-next-to-devices","Deploying Node-RED Next to Devices",[10,33,34,35,40,41,44],{},"One common issue in IoT deployments is that device instances of Node-RED often communicate with unsecure devices or networks. To mitigate security risks and ensure data protection, it's common to deploy Node-RED in close proximity to these devices. The FlowFuse platform uses ",[36,37,39],"a",{"href":38},"\u002Fplatform\u002Fdevice-agent\u002F","device agents"," that communicate back to the platform via a reverse tunnel over port 443. This setup requires only one firewall rule: allowing outbound connections from the ",[36,42,43],{"href":38},"device agent"," running Node-RED to the FlowFuse platform, significantly minimizing security risks while enabling remote monitoring, flow editing, and configuration deployment at scale.",[14,46,48],{"id":47},"deploying-node-red-instances-within-the-flowfuse-platform","Deploying Node-RED Instances Within the FlowFuse Platform",[10,50,51],{},"Not all instances of Node-RED need to be deployed at the edge and can be deployed anywhere. FlowFuse offers this flexibility in cases where users prefer or require deploying their Node-RED instances within the platform itself. This capability allows users to focus on developing and managing their applications without worrying about the underlying infrastructure.",[14,53,55],{"id":54},"conclusion","Conclusion",[10,57,58],{},"FlowFuse addresses scalability challenges in Node-RED deployments by providing an easy-to-use platform that enables users to manage multiple instances at scale while maintaining security and performance. By understanding the differences between a FlowFuse instance and a device instance, you can make informed decisions about your deployment strategy and leverage the full potential of Node-RED for your applications. Stay tuned for our upcoming blogs where we will dive deeper into the areas of security, dev ops, and backup solutions provided by FlowFuse.",{"title":60,"searchDepth":61,"depth":61,"links":62},"",2,[63,64,65,66,67],{"id":16,"depth":61,"text":17},{"id":23,"depth":61,"text":24},{"id":30,"depth":61,"text":31},{"id":47,"depth":61,"text":48},{"id":54,"depth":61,"text":55},"md",{"navTitle":5,"excerpt":70},{"type":7,"value":71},[72],[10,73,12],{},true,"\u002Fblog\u002F2024\u002F03\u002Fscaling-node-red-devices-vs-flowfuse-instance",{"title":5,"description":12},"blog\u002F2024\u002F03\u002Fscaling-node-red-devices-vs-flowfuse-instance","cATtJke-2JyBUDI2MXMSZSwW2C4s_0Hyt9-gHh13Fuk",1780132426565]