Skip to content
FME Blog

4 Reasons to Use Remote Engines for FME Flow

Remote Engine Services in FME Flow allows you to deploy FME anywhere. Learn why this can be beneficial.
Earth Data Sharing Earth Data Sharing

In today’s digital landscape, data is increasingly distributed across multiple data centers and on-premises locations. The rise of the Internet of Things (IoT), with devices and data scattered all over the internet, means more people need to run FME data integration workflows at the edge. Remote Engines are an ideal solution for supporting distributed, hybrid, or edge deployments.

In a nutshell, Remote Engines allow you to deploy FME anywhere. This has several advantages:

1. Better Performance

We always recommend deploying FME close to the data. With Remote Engines, jobs can run near the data source, regardless of where it’s stored or collected, reducing latency and improving processing times. Whether data is stored locally or collected from IoT devices across the internet, Remote Engines help ensure that processing happens with maximum efficiency.

2. Higher Security

A primary FME Flow installation can remain protected behind a firewall while jobs are executed on servers outside your network. This setup enhances security by minimizing exposure and maintaining control over sensitive data.

3. Greater Flexibility

On-premises workflows can still run locally, while cloud-optimized workflows can be scheduled or triggered on cloud-hosted Remote Engines. For organizations with a multi-cloud strategy, this means managing just one FME deployment to support both internal and cloud-based workflows.

4. Easier Management

For organizations with a global private network, Remote Engines simplify FME deployment and management. Administrators can manage a single FME instance and deploy Remote Engines throughout the network close to the data.

Consider a company with regional offices worldwide. Rather than deploying FME Flow in each region, they could maintain one master FME Flow and deploy Remote Engines in each region. This means less maintenance overhead with only one FME Flow instance to manage, and since all jobs go through one FME Flow, it’s easier to understand how FME is being utilized and therefore optimize resources.

Getting Started with Remote Engine Services in FME Flow

Remote Engines Services is a powerful tool for optimizing FME Flow deployments. It can enhance performance, security, flexibility, and administration, making it an excellent choice for organizations handling distributed data.

Remote Engine Services allows you to use queues to run jobs on FME Flow instances closest to your data while bypassing Queue Control rules. Remote Engines can be within your network, outside your network on accessible endpoints, or in the cloud.

Learn more about Remote Engine Services in the FME documentation and in the article Leverage Remote Engine Service in FME Flow.

Safe product icons
Reach out and get started with FME today

Real change is just a platform away.