[{"data":1,"prerenderedAt":94},["ShallowReactive",2],{"blog-\u002Fblog\u002F2024\u002F03\u002Fscaling-node-red-devices-vs-flowfuse-instance":3,"blog-all-for-related":93},{"id":4,"title":5,"authors":6,"body":8,"cta":71,"date":72,"description":73,"extension":74,"image":75,"lastUpdated":71,"meta":76,"navigation":81,"path":82,"seo":83,"sitemap":84,"stem":85,"subtitle":86,"tags":87,"tldr":71,"video":71,"__hash__":92},"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",[7],"grey-dziuba",{"type":9,"value":10,"toc":61},"minimark",[11,15,20,23,27,30,34,47,51,54,58],[12,13,14],"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.",[16,17,19],"h2",{"id":18},"scalability-challenges-with-traditional-node-red-deployments","Scalability Challenges with Traditional Node-RED Deployments",[12,21,22],{},"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.",[16,24,26],{"id":25},"the-role-of-flowfuse-as-an-orchestration-tool","The Role of FlowFuse as an Orchestration Tool",[12,28,29],{},"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.",[16,31,33],{"id":32},"deploying-node-red-next-to-devices","Deploying Node-RED Next to Devices",[12,35,36,37,42,43,46],{},"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 ",[38,39,41],"a",{"href":40},"\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 ",[38,44,45],{"href":40},"device agent"," running Node-RED to the FlowFuse platform, significantly minimizing security risks while enabling remote monitoring, flow editing, and configuration deployment at scale.",[16,48,50],{"id":49},"deploying-node-red-instances-within-the-flowfuse-platform","Deploying Node-RED Instances Within the FlowFuse Platform",[12,52,53],{},"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.",[16,55,57],{"id":56},"conclusion","Conclusion",[12,59,60],{},"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":62,"searchDepth":63,"depth":63,"links":64},"",4,[65,67,68,69,70],{"id":18,"depth":66,"text":19},2,{"id":25,"depth":66,"text":26},{"id":32,"depth":66,"text":33},{"id":49,"depth":66,"text":50},{"id":56,"depth":66,"text":57},null,"2024-03-25","With FlowFuse, Node-RED instances can be scaled and managed easily.","md","\u002Fblog\u002F2024\u002F03\u002Fimages\u002Fscaling-node-red-with-flowfuse.png",{"excerpt":77},{"type":9,"value":78},[79],[12,80,14],{},true,"\u002Fblog\u002F2024\u002F03\u002Fscaling-node-red-devices-vs-flowfuse-instance",{"title":5,"description":73},{"loc":82},"blog\u002F2024\u002F03\u002Fscaling-node-red-devices-vs-flowfuse-instance","Managing your Node-RED instances is easier with FlowFuse.",[88,89,90,91],"posts","flowfuse","device instance","scaling node-red","ty9YgAUpIFJv7TRRbKEJzyRCevDUj4fQiOq-tRGO9YY",[],1785528690547]