Alternatives to Talend logo

Alternatives to Talend

Spring Batch, Alooma, Airflow, Matillion, and Apache Spark are the most popular alternatives and competitors to Talend.
298
228
+ 1
0

What is Talend and what are its top alternatives?

It is an open source software integration platform helps you in effortlessly turning data into business insights. It uses native code generation that lets you run your data pipelines seamlessly across all cloud providers and get optimized performance on all platforms.
Talend is a tool in the Big Data Tools category of a tech stack.

Top Alternatives to Talend

  • Spring Batch
    Spring Batch

    It is designed to enable the development of robust batch applications vital for the daily operations of enterprise systems. It also provides reusable functions that are essential in processing large volumes of records, including logging/tracing, transaction management, job processing statistics, job restart, skip, and resource management. ...

  • Alooma
    Alooma

    Get the power of big data in minutes with Alooma and Amazon Redshift. Simply build your pipelines and map your events using Alooma’s friendly mapping interface. Query, analyze, visualize, and predict now. ...

  • Airflow
    Airflow

    Use Airflow to author workflows as directed acyclic graphs (DAGs) of tasks. The Airflow scheduler executes your tasks on an array of workers while following the specified dependencies. Rich command lines utilities makes performing complex surgeries on DAGs a snap. The rich user interface makes it easy to visualize pipelines running in production, monitor progress and troubleshoot issues when needed. ...

  • Matillion
    Matillion

    It is a modern, browser-based UI, with powerful, push-down ETL/ELT functionality. With a fast setup, you are up and running in minutes. ...

  • Apache Spark
    Apache Spark

    Spark is a fast and general processing engine compatible with Hadoop data. It can run in Hadoop clusters through YARN or Spark's standalone mode, and it can process data in HDFS, HBase, Cassandra, Hive, and any Hadoop InputFormat. It is designed to perform both batch processing (similar to MapReduce) and new workloads like streaming, interactive queries, and machine learning. ...

  • AWS Glue
    AWS Glue

    A fully managed extract, transform, and load (ETL) service that makes it easy for customers to prepare and load their data for analytics. ...

  • Splunk
    Splunk

    It provides the leading platform for Operational Intelligence. Customers use it to search, monitor, analyze and visualize machine data. ...

  • Amazon Athena
    Amazon Athena

    Amazon Athena is an interactive query service that makes it easy to analyze data in Amazon S3 using standard SQL. Athena is serverless, so there is no infrastructure to manage, and you pay only for the queries that you run. ...

Talend alternatives & related posts

Spring Batch logo

Spring Batch

167
227
0
A lightweight, comprehensive batch framework
167
227
+ 1
0
PROS OF SPRING BATCH
    Be the first to leave a pro
    CONS OF SPRING BATCH
      Be the first to leave a con

      related Spring Batch posts

      Alooma logo

      Alooma

      24
      47
      0
      Integrate any data source like databases, applications, and any API - with your own Amazon Redshift
      24
      47
      + 1
      0
      PROS OF ALOOMA
        Be the first to leave a pro
        CONS OF ALOOMA
          Be the first to leave a con

          related Alooma posts

          Airflow logo

          Airflow

          1.5K
          2.5K
          125
          A platform to programmaticaly author, schedule and monitor data pipelines, by Airbnb
          1.5K
          2.5K
          + 1
          125
          PROS OF AIRFLOW
          • 50
            Features
          • 14
            Task Dependency Management
          • 12
            Beautiful UI
          • 12
            Cluster of workers
          • 10
            Extensibility
          • 6
            Open source
          • 5
            Complex workflows
          • 5
            Python
          • 3
            Good api
          • 3
            Apache project
          • 3
            Custom operators
          • 2
            Dashboard
          CONS OF AIRFLOW
          • 2
            Running it on kubernetes cluster relatively complex
          • 2
            Open source - provides minimum or no support
          • 1
            Logical separation of DAGs is not straight forward
          • 1
            Observability is not great when the DAGs exceed 250

          related Airflow posts

          Shared insights
          on
          JenkinsJenkinsAirflowAirflow

          I am looking for an open-source scheduler tool with cross-functional application dependencies. Some of the tasks I am looking to schedule are as follows:

          1. Trigger Matillion ETL loads
          2. Trigger Attunity Replication tasks that have downstream ETL loads
          3. Trigger Golden gate Replication Tasks
          4. Shell scripts, wrappers, file watchers
          5. Event-driven schedules

          I have used Airflow in the past, and I know we need to create DAGs for each pipeline. I am not familiar with Jenkins, but I know it works with configuration without much underlying code. I want to evaluate both and appreciate any advise

          See more
          Shared insights
          on
          AWS Step FunctionsAWS Step FunctionsAirflowAirflow

          I am working on a project that grabs a set of input data from AWS S3, pre-processes and divvies it up, spins up 10K batch containers to process the divvied data in parallel on AWS Batch, post-aggregates the data, and pushes it to S3.

          I already have software patterns from other projects for Airflow + Batch but have not dealt with the scaling factors of 10k parallel tasks. Airflow is nice since I can look at which tasks failed and retry a task after debugging. But dealing with that many tasks on one Airflow EC2 instance seems like a barrier. Another option would be to have one task that kicks off the 10k containers and monitors it from there.

          I have no experience with AWS Step Functions but have heard it's AWS's Airflow. There looks to be plenty of patterns online for Step Functions + Batch. Do Step Functions seem like a good path to check out for my use case? Do you get the same insights on failing jobs / ability to retry tasks as you do with Airflow?

          See more
          Matillion logo

          Matillion

          45
          63
          0
          An ETL Tool for BigData
          45
          63
          + 1
          0
          PROS OF MATILLION
            Be the first to leave a pro
            CONS OF MATILLION
              Be the first to leave a con

              related Matillion posts

              Apache Spark logo

              Apache Spark

              2.7K
              3.3K
              139
              Fast and general engine for large-scale data processing
              2.7K
              3.3K
              + 1
              139
              PROS OF APACHE SPARK
              • 60
                Open-source
              • 48
                Fast and Flexible
              • 8
                Great for distributed SQL like applications
              • 8
                One platform for every big data problem
              • 6
                Easy to install and to use
              • 3
                Works well for most Datascience usecases
              • 2
                In memory Computation
              • 2
                Interactive Query
              • 2
                Machine learning libratimery, Streaming in real
              CONS OF APACHE SPARK
              • 3
                Speed

              related Apache Spark posts

              Eric Colson
              Chief Algorithms Officer at Stitch Fix · | 21 upvotes · 2.7M views

              The algorithms and data infrastructure at Stitch Fix is housed in #AWS. Data acquisition is split between events flowing through Kafka, and periodic snapshots of PostgreSQL DBs. We store data in an Amazon S3 based data warehouse. Apache Spark on Yarn is our tool of choice for data movement and #ETL. Because our storage layer (s3) is decoupled from our processing layer, we are able to scale our compute environment very elastically. We have several semi-permanent, autoscaling Yarn clusters running to serve our data processing needs. While the bulk of our compute infrastructure is dedicated to algorithmic processing, we also implemented Presto for adhoc queries and dashboards.

              Beyond data movement and ETL, most #ML centric jobs (e.g. model training and execution) run in a similarly elastic environment as containers running Python and R code on Amazon EC2 Container Service clusters. The execution of batch jobs on top of ECS is managed by Flotilla, a service we built in house and open sourced (see https://github.com/stitchfix/flotilla-os).

              At Stitch Fix, algorithmic integrations are pervasive across the business. We have dozens of data products actively integrated systems. That requires serving layer that is robust, agile, flexible, and allows for self-service. Models produced on Flotilla are packaged for deployment in production using Khan, another framework we've developed internally. Khan provides our data scientists the ability to quickly productionize those models they've developed with open source frameworks in Python 3 (e.g. PyTorch, sklearn), by automatically packaging them as Docker containers and deploying to Amazon ECS. This provides our data scientist a one-click method of getting from their algorithms to production. We then integrate those deployments into a service mesh, which allows us to A/B test various implementations in our product.

              For more info:

              #DataScience #DataStack #Data

              See more
              Conor Myhrvold
              Tech Brand Mgr, Office of CTO at Uber · | 7 upvotes · 1.3M views

              Why we built Marmaray, an open source generic data ingestion and dispersal framework and library for Apache Hadoop :

              Built and designed by our Hadoop Platform team, Marmaray is a plug-in-based framework built on top of the Hadoop ecosystem. Users can add support to ingest data from any source and disperse to any sink leveraging the use of Apache Spark . The name, Marmaray, comes from a tunnel in Turkey connecting Europe and Asia. Similarly, we envisioned Marmaray within Uber as a pipeline connecting data from any source to any sink depending on customer preference:

              https://eng.uber.com/marmaray-hadoop-ingestion-open-source/

              (Direct GitHub repo: https://github.com/uber/marmaray Kafka Kafka Manager )

              See more
              AWS Glue logo

              AWS Glue

              429
              759
              9
              Fully managed extract, transform, and load (ETL) service
              429
              759
              + 1
              9
              PROS OF AWS GLUE
              • 9
                Managed Hive Metastore
              CONS OF AWS GLUE
                Be the first to leave a con

                related AWS Glue posts

                Pardha Saradhi
                Technical Lead at Incred Financial Solutions · | 6 upvotes · 73.5K views

                Hi,

                We are currently storing the data in Amazon S3 using Apache Parquet format. We are using Presto to query the data from S3 and catalog it using AWS Glue catalog. We have Metabase sitting on top of Presto, where our reports are present. Currently, Presto is becoming too costly for us, and we are looking for alternatives for it but want to use the remaining setup (S3, Metabase) as much as possible. Please suggest alternative approaches.

                See more

                Trying to establish a data lake(or maybe puddle) for my org's Data Sharing project. The idea is that outside partners would send cuts of their PHI data, regardless of format/variables/systems, to our Data Team who would then harmonize the data, create data marts, and eventually use it for something. End-to-end, I'm envisioning:

                1. Ingestion->Secure, role-based, self service portal for users to upload data (1a. bonus points if it can preform basic validations/masking)
                2. Storage->Amazon S3 seems like the cheapest. We probably won't need very big, even at full capacity. Our current storage is a secure Box folder that has ~4GB with several batches of test data, code, presentations, and planning docs.
                3. Data Catalog-> AWS Glue? Azure Data Factory? Snowplow? is the main difference basically based on the vendor? We also will have Data Dictionaries/Codebooks from submitters. Where would they fit in?
                4. Partitions-> I've seen Cassandra and YARN mentioned, but have no experience with either
                5. Processing-> We want to use SAS if at all possible. What will work with SAS code?
                6. Pipeline/Automation->The check-in and verification processes that have been outlined are rather involved. Some sort of automated messaging or approval workflow would be nice
                7. I have very little guidance on what a "Data Mart" should look like, so I'm going with the idea that it would be another "experimental" partition. Unless there's an actual mart-building paradigm I've missed?
                8. An end user might use the catalog to pull certain de-identified data sets from the marts. Again, role-based access and self-service gui would be preferable. I'm the only full-time tech person on this project, but I'm mostly an OOP, HTML, JavaScript, and some SQL programmer. Most of this is out of my repertoire. I've done a lot of research, but I can't be an effective evangelist without hands-on experience. Since we're starting a new year of our grant, they've finally decided to let me try some stuff out. Any pointers would be appreciated!
                See more
                Splunk logo

                Splunk

                554
                924
                14
                Search, monitor, analyze and visualize machine data
                554
                924
                + 1
                14
                PROS OF SPLUNK
                • 2
                  Ability to style search results into reports
                • 2
                  Alert system based on custom query results
                • 2
                  API for searching logs, running reports
                • 2
                  Query engine supports joining, aggregation, stats, etc
                • 1
                  Query any log as key-value pairs
                • 1
                  Splunk language supports string, date manip, math, etc
                • 1
                  Granular scheduling and time window support
                • 1
                  Custom log parsing as well as automatic parsing
                • 1
                  Dashboarding on any log contents
                • 1
                  Rich GUI for searching live logs
                CONS OF SPLUNK
                • 1
                  Splunk query language rich so lots to learn

                related Splunk posts

                Shared insights
                on
                KibanaKibanaSplunkSplunkGrafanaGrafana

                I use Kibana because it ships with the ELK stack. I don't find it as powerful as Splunk however it is light years above grepping through log files. We previously used Grafana but found it to be annoying to maintain a separate tool outside of the ELK stack. We were able to get everything we needed from Kibana.

                See more
                Shared insights
                on
                SplunkSplunkElasticsearchElasticsearch

                We are currently exploring Elasticsearch and Splunk for our centralized logging solution. I need some feedback about these two tools. We expect our logs in the range of upwards > of 10TB of logging data.

                See more
                Amazon Athena logo

                Amazon Athena

                494
                783
                47
                Query S3 Using SQL
                494
                783
                + 1
                47
                PROS OF AMAZON ATHENA
                • 15
                  Use SQL to analyze CSV files
                • 8
                  Glue crawlers gives easy Data catalogue
                • 7
                  Cheap
                • 5
                  Query all my data without running servers 24x7
                • 4
                  No data base servers yay
                • 3
                  Easy integration with QuickSight
                • 2
                  Query and analyse CSV,parquet,json files in sql
                • 2
                  Also glue and athena use same data catalog
                • 1
                  No configuration required
                • 0
                  Ad hoc checks on data made easy
                CONS OF AMAZON ATHENA
                  Be the first to leave a con

                  related Amazon Athena posts

                  I use Amazon Athena because similar to Google BigQuery , you can store and query data easily. Especially since you can define data schema in the Glue data catalog, there's a central way to define data models.

                  However, I would not recommend for batch jobs. I typically use this to check intermediary datasets in data engineering workloads. It's good for getting a look and feel of the data along its ETL journey.

                  See more

                  Hi all,

                  Currently, we need to ingest the data from Amazon S3 to DB either Amazon Athena or Amazon Redshift. But the problem with the data is, it is in .PSV (pipe separated values) format and the size is also above 200 GB. The query performance of the timeout in Athena/Redshift is not up to the mark, too slow while compared to Google BigQuery. How would I optimize the performance and query result time? Can anyone please help me out?

                  See more