FME Alternatives

From my perspective as a Principal Cloud Infrastructure Analyst, AWS Glue is a strong and exceptional fit for managed ETL in our Data Mesh context, but it requires disciplined engineering around governance, cost control, and operational runbooks. Reliability has been good when we enforce network connection standards, IAM role standards, and repeatable aggregation/deployment patterns. Where complexity shows up is not in basic ETL, but in scale behavior: schema drift, crawler edge cases, cross-account catalog sync, and differences between small dev datasets and real production distributions. Reliability & Uptime: Glue jobs and notebooks have been stable for batch pipelines (Landing Parquet to Raw Iceberg), especially after standardizing session/job settings, VPC connections, and naming conventions. I also found that explicitly using Glue 5.0 for Lake Formation fine-grained access reduced friction compared to Glue 4.0-era workarounds. Support Quality: Support has been effective when issues are concrete (permissions, crawler configurations, Iceberg parameters, job retries), but root-cause analysis still depends heavily on in-house expertise and structured troubleshooting. The turn-around in these scenarios, or especially when the solution requires a feature enhancement, can be a blocker and something to consider. Integration Success: I have seen Glue integrations work well with Lake Formation, Athena, Data Catalog/Data Mesh patterns, and Snowflake interoperability designs. In practice, data integration quality improves when ownership boundaries are clear (single writer principle, explicit account/environment segregation, and defined IAM trust patterns) Business Impact: Glue has allowed us to move faster on governed data ingestion, data modeling and data transformation, while maintaining security guardrails and metadata consistency as first-class concerns. Scenario 1: I worked through Glue 4.0/earlier limitations where column-level filtering was problematic for some Lake Formation-tagged datasets, and I used Athena-based workarounds (direct queries/JDBC) where needed. Moving to Glue 5.0 with proper session configurations and Lake Formation fine-grained settings materially simplified operations and reduced workaround overhead. Scenario 2: I dealt with crawler quality issues in Data Mesh onboarding (table over-consolidation, schema migration, partition/schema inconsistencies, and KMS-key-related read problems). We have improved reliability by tightening the S3 layout conventions, exclusion patterns, crawl scope, and schema update controls, plus targeted re-crawls and manual DDL fallback where necessary.

Informatica Powercenter is a good ETL tool. Support extraction, transform and load the data to different targets from heterogeneous sources. It is a very reliable tool for data engineers to load data into data warehouses.

I am not an end-user of Ab Initio and cannot really speak to its capabilities as an ETL tool. I manage the infrastructure that delivers Ab Initio to our end-users so my perspective is only on those aspects which I touch. As far as managing installation and patching and maintaining the software, the processes are a bit legacy. However, one of the projects we're working with our support representatives is modernizing that, so that's definitely on their plates as something they're working on. But that's the main thing that makes Ab Initio so great is the relationship they maintain with us, which has been nothing but phenomenal the entire time I've been on the project and this is echoed by others who have been on the project much longer than me. Ab Initio truly makes us feel like a customer where most other vendors just don't.

We are using SQL Server and SSIS for our DWH, and overall, I am quite happy with it. The Ui is pretty user-friendly, so it is easy to work with on a daily basis. Building solutions using stored procedures, SQL jobs, and SSIS is quite straight forward and doesn't take too much effort. It really helps simplify our data processing dan integration. So far it has been stable and reliable, with only some minor tuning needed here and there.

Our organization leverages Fivetran to hydrate our BigQuery data lake. Currently, Fivetran is used for incremental data extraction from over 40 SaaS and platform sources, while HVR supports real-time replication of over 400 tables from two database sources, with additional sources currently being onboarded. Fivetran products play a critical role in our data landscape, as data ingestion is the first - and foundational - step in our Data & Analytics lifecycle. If the data is not reliable at this stage, the value of downstream analytics is significantly reduced. After more than 3 years of partnership, our experience with Fivetran has been very positive, and we look forward to continuing to strengthen and expand this collaboration.

The solution is stable, innovative and has a very broad functional coverage. It replaces many components that we would otherwise have had to assemble. The platform's evolution is satisfactory, and the integration of new features happens at a satisfactory pace. The publisher listens to its clients, the support is of very high quality, as are the documentation resources. Additionally, once you become a client, access to online training and certifications is included.

It's a functional platform that gets the job done, but it definitely feels like a "jack of all trades, master of none" situation. On one hand, it's great to have everything in the cloud without managing servers, and the security features are robust enough for our compliance needs. On the other hand, the transition from legacy on-prem solutions to this cloud version hasn't been as seamless as id hoped for. We often find ourselves stuck in the middle with Talend because while, yes, it's more powerful than a basic ingestion tool, it's also more restrictive than a pure code environment. It's a solid 3-star choice for a mid to large company that wants a "safe" enterprise bet, but it lacks the "wow" factor or the agility of some newer, leaner competitors.

When we started using Snowflake in 2018, we chose Matillion ETL as our tool of choice for data integration and orchestration of data pipelines. We are currently in the process of migration. We have been using Matillion as our main data integration and data transformation tool for our Snowflake data warehouse to enable data-driven initiatives in B2C sales and marketing. We have been processing mostly batch data. As our team consists of people with strong programming and data backgrounds as well as less tech-savvy users, Matillion facilitates easy collaboration between the two. The representation of a data pipeline as a flow chart of components with customizable properties on a canvas is easily readable even without a technical background. Some complex SQL usage patterns have no equivalent component in Matillion ELT but can be implemented using an SQL component. Sampling at any step of the data pipeline makes ongoing validation of the data transformation and debugging very easy. Matillion ETL offers connectors to integrate with most data sources relevant to our use cases. Seamless integration of Python in the orchestration jobs, offers the ability for API calls should a native connector to any source system be missing. Rollout on both Azure and AWS was well documented and easily done. In general, Matillion ETL integrates well into our workflow, however the GIT integration is lacking some features to make it truly elegant, especially for users who are less used to it. We onboarded other teams on Snowflake and Matillion ELT who were quickly able to work independently after an early short period of enablement and support. In total, our Matillion ETL instance hosted 15-20 data engineers across several teams. As we did not have a data warehouse beforehand, we cannot supply comparative metrics. Snowflake and Matillion outright enabled us for the first time to conduct truly data-driven use cases with state of the art technology solutions.