AWS Glue vs. TIBCO EBX

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

One of the scenarios where TIBCO EBX is best adapted is for the unification of records to form the Golden Record and equivalence management, this together with the end user's own administration according to the excellent functionality of the creation of test flows. So far I have not found a scenario where we can adapt TIBCO EBX according to the needs that have been presented to us.

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

• Unification of records to form golden records
• Centralize master catalogs
• Excellent administration with approval and publication flows.

Incentivized

• 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

• Improve access to information through API for integrations.

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

TIBCO EBX was our first option for implementation in our organization since we know the quality of TIBCO products and verifying their positioning in the evaluation quadrants, it was not necessary for us to evaluate any other products for these purposes in our organization. The implementation of TIBCO EBX has been a fundamental piece for the technological transformation of the organization since its benefits have been really good.

Incentivized

• 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

• Streamline the organization's information management.
• Implementation of important business rules in the TIBCO EBX to unify the information
• Efficient information for analytical reports with cleaner information for organization.

Incentivized