-
Notifications
You must be signed in to change notification settings - Fork 18
June's webinar page #3284
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
June's webinar page #3284
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
fd1d5c5
Creae june webinar page
3c779cc
Optimised images with calibre/image-actions
github-actions[bot] 059f65e
Fix capitalization and add it to the events banner
66ee217
Full Abstract
707f083
Call out "reliability"
5b421ac
Update src/webinars/2025/node-red-why-and-when-for-cloud-and-edge.md
joepavitt File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,5 +1,5 @@ | ||
| - type: "Webinar" | ||
| title: "Develop, Manage, and Deploy Complex Node-RED Projects at Scale" | ||
| title: "Node-RED - Why and When, for Cloud and Edge" | ||
| buttonText: "Register now" | ||
| link: "/webinars/2025/develop-manage-and-deploy-complex-node-red-projects-at-scale-with-flowfuse/" | ||
| expire: "2025-05-27T16:00:00Z" | ||
| link: "/webinars/2025/node-red-why-and-when-for-cloud-and-edge/" | ||
| expire: "2025-06-25T16:00:00Z" |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
43 changes: 43 additions & 0 deletions
43
src/webinars/2025/node-red-why-and-when-for-cloud-and-edge.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,43 @@ | ||
| --- | ||
| title: "Node-RED - Why and When, for Cloud and Edge" | ||
| subtitle: | ||
| meta: | ||
| description: Master how to optimize your Node-RED applications for availability, performance and quality. Discover the common architectures of FlowFuse customers who are running Node-RED in production environments. With options to host Instances in the Cloud, Self-Host or deploy to the Edge, discover what factors you should be considering when architecting your own deployments. | ||
| image: /images/webinars/node-red-why-and-when-for-cloud-and-edge.jpg | ||
| date: 2025-06-25 | ||
| time: 17:00 CET (11:00am ET) | ||
| duration: 60 | ||
| video: | ||
| hosts: ["joe-pavitt", "stephen-mclaughlin"] | ||
| hubspot: | ||
| formId: b34f3bed-a9f8-4135-a520-a0cc5b0c2578 | ||
| downloadFormId: | ||
| --- | ||
|
|
||
| **Master how to optimize your Node-RED applications for availability, performance and quality.** | ||
|
|
||
| Discover the common architectures of FlowFuse customers who are running Node-RED in production environments. | ||
|
|
||
| <!--more--> | ||
| Choosing the right architecture isn’t just a matter of preference — it has a direct impact on scalability, reliability, and operational efficiency. A single centralized Node-RED instance may seem simple to manage at first, but it can become a bottleneck as workloads grow, introducing risks like a single point of failure or degraded performance. In this webinar, we'll highlight why many teams are moving toward distributed architectures — like running one instance per device or per workflow — to better align with production demands. | ||
|
|
||
| With options to host Instances in the Cloud, Self-Host or deploy to the Edge, discover what factors you should be considering when architecting your own deployments. | ||
|
|
||
| ## Node-RED Architectures | ||
|
|
||
| We'll cover the pros, cons, opportunities and limitations of running Node-RED in a variety of different architectures. Specifically, we'll cover: | ||
|
|
||
| - **Cloud-Hosted Node-RED:** How can you secure your Node-RED instances in the cloud, how well does Node-RED scale for larger workloads and what design and architectural patterns are best suited to this environment. | ||
| - **Node-RED at the Edge:** What capabilities are available when running Node-RED at the edge, what use cases best fit this architecture and how can you go about doing this yourself. | ||
|
|
||
| Examples will be shown too that discuss where a split architecture is important, with some Instances running in the Cloud and some running at-Edge, and how best to communicate between these Instances to ensure scalability, reliability and security in your production environments. | ||
|
|
||
| ## Deploying with FlowFuse | ||
|
|
||
| At a higher-level, we'll then explore how FlowFuse provides infrastructure to support management of these different architectures and even cover the choice of where to deploy FlowFuse itself, as that can have architectural consequences, with three core options available: | ||
|
|
||
| - **Cloud:** Available to sign up to now, FlowFuse Cloud is our Cloud-hosted Platform and Node-RED Instances are hosted in the Cloud. | ||
| - **Self-Hosted:** Where FlowFuse is deployed in the Cloud, and Node-RED Instances are hosted on-premises or in a data centre closest to your users. | ||
| - **Dedicated:** Where FlowFuse is deployed in the Cloud, and Node-RED Instances are hosted on-premises or in a data centre closest to your users. | ||
|
|
||
| The team will detail example customer projects, exploring the capabilities available with running Node-RED applications on FlowFuse. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.