AWS Glue vs. Oracle Warehouse Builder

One of AWS Glue's most notable features that aid in the creation and transformation of data is its data catalog. Support, scheduling, and the automation of the data schema recognition make it superior to its competitors aside from that. It also integrates perfectly with other AWS tools. The main restriction may be integrated with systems outside of the AWS environment. It functions flawlessly with the current AWS services but not with other goods. Another potential restriction that comes to mind is that glue operates on a spark, which means the engineer needs to be conversant in the language.

Incentivized

The best place for Oracle Warehouse Builder is at the business IT level. It's not suited for business-level users. They are easy confused. One way to reduce the confusion for the developers is to set up the workspaces based on the requirements that are discovered in design sessions. Once this is complete, the implementation of Oracle Warehouse Builder can take flight and be successful.

Incentivized

• It is extremely fast, easy, and self-intuitive. Though it is a suite of services, it requires pretty less time to get control over it.
• As it is a managed service, one need not take care of a lot of underlying details. The identification of data schema, code generation, customization, and orchestration of the different job components allows the developers to focus on the core business problem without worrying about infrastructure issues.
• It is a pay-as-you-go service. So, there is no need to provide any capacity in advance. So, it makes scheduling much easier.

Incentivized

• Easy transformation.
• Easy implementation from Oracle to Oracle systems.
• Ease of usage and easy to learn.
• Starting component of metadata management.

Incentivized

• In-Stream schema registries feature people can not use this more efficiently
• in Connections feature they can add more connectors as well
• The crucial problem with AWS Glue is that it only works with AWS.

Incentivized

• What I noticed is that sometimes OWB doesn't generate the best SQL in the package especially when there are a high number of source tables in the ETL. It would be nice if ETL developers were allowed to update the generated packages in the database directly.
• Another thing - moving OWB ETLs from one database to another one could be easier - for example it would be nice to just copy the generated packages from one database to the other one without doing the deployment of these ETLs through OWB.

Incentivized

While easy to set up and manage monitoring for large datasets, its complexity can be a barrier for new users. Integration with AWS Ecosystem, Managed Monitoring, Dashboards and monitoring tools for AWS Glue are generally easy to set up and maintain, Automated Data Pipelines. Automates data pipeline creation, making it efficient for certain data integration

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

AWS Glue is a fully managed ETL service that automates many ETL tasks, making it easier to set AWS Glue simplifies ETL through a visual interface and automated code generation.

Ab>initio, IBM Datastage 8.0

Incentivized

• We are using GLUE for our ETL purpose. it’s ease with other our AWS services makes our ROI, 100% ROI.
• One missing piece was compatibility with other data source for which we found a work around and made our data source as S3 only, so our dependencies on other data source is also reducing

Incentivized

• It improved understanding of ETL functions. Data is consistent. The speed is pretty good.

Incentivized