AWS Glue vs. IBM InfoSphere Information Server

When the data which requires ETL has different formats, schema, and volume, this service suits them best. So, when the volume is not consistent (typical use-case of healthcare and online shopping), AWS Glue can be the prime choice. When the data is available in both batch and streaming mode, the developer needs to generate a separate codebase. This increases the source code management efforts. So, prefer to go with Glue when the nature of the data is the same (either batched or streamed).

Incentivized

You can use infosphere: -If you have multiple targets and source systems and they are different than each other. -If your infostructure is so big and unplaned well so you can't find what you want to see. -If your databases not so strong to process your data

Incentivized

• After data cleansing, the team also implemented the best practices for using AWS platform services as a Data Lake, such as job bookmarking for AWS Glue jobs, proper delimiter for the AWS Glue crawlers, partitioning in AWS S3, and transformation to parquet file for compression and faster querying time in Amazon Athena.
• Data modernization through combining data from multiple sources into a functioning datasets, rebuilding DW, and resctructuring data sources.
• Aims to lessen customer complaints, eliminate manual data extraction requests via SR from different data sources, and Increase accuracy, consistency and speed up reconciliation process.

Incentivized

• It is very strong to make transformations/data derivations
• It is very easy to connect to various external data sources. It has an interface (stages) for each connection that simplifies the task
• It is a stable platform. And that parallelism helps make it fast for loading, if the process is well designed

• It’s integration with other cloud vendors is bit difficult
• If it can support non SQL based databases as well, it would be powerful.
• Real time data synchronisation in data source is missing

Incentivized

• Lack of a strong web development environment.
• Metadata propagation in Jobs is somewhat complex.
• The possibility to develop jobs in Parallel and/or Server Engines is confusing.

• Scale of implementation
• IBM techsupport

Incentivized

I personally found it very usable for a data engineer's day job, particularly for performing ETL and managing the data pipelines.

Incentivized

Amazon responds in good time once the ticket has been generated but needs to generate tickets frequent because very few sample codes are available, and it's not cover all the scenarios.

Incentivized

The cataloging of data objects is the best in the case of AWS Glue. We use AWS Glue in all of our data pipelines to sync external and internal data sources and to automatically produce SQL-based ETL based on AWS Glue catalog objects. Integration with Amazon products is the other advantage.

Incentivized

I particularly believe that Information Server, especially DataStage, is superior in many aspects to the Oracle Data Integrator tool. Several market analysts such as Gartner and / or Forrester better position DataStage on the Oracle solution.

• Positive Impact :- after ETL we can able to do some kind of automation
• Negative :- At some point of time it can hamper the cost but not really

Incentivized

• Information Server can positively impact the costs of companies by increasing the productivity of development and therefore reduce their time and costs. It is estimated that DataStage can increase a developer's productivity by 40% on average.
• Better data governance
• Improve data quality and reduce bad data impacts

Incentivized