AWS Glue Reviews

I primarily use AWS Glue as a lightweight ETL to migrate our existing on-prem workloads to a cloud environment without looking at a lot of migration paths. 

AWS Glue served the purpose of migrating our on-prem workloads to a cloud environment without involving a heavy load. It ensured that we were able to test every migrated component independently.

AWS Glue's best features are scalability and cloud-based features.

AWS Glue would be improved by making it easier to switch from single to multi-cloud.

I've been using AWS Glue for eighteen months.

I would rate AWS Glue's scalability eight out of ten, as it still has some room to improve.

AWS Glue is straightforward to implement, and you won't see any technical complexity if you're from a development background.

We also considered Airflow, but Glue was a better fit for our engineering-heavy workloads because we wanted a serverless option.

I would rate AWS Glue eight out of ten.

My colleagues work with Spark, PySpark, and Scala as programming languages for writing complex aggregations. They have a repository in order to have a general view of all the sources and jobs on the platform and AWS Glue is very helpful.

AWS Glue is a good solution for developers, they have the ability to write code in different languages and other software.

The interface for AWS Glue could improve, they do not put a lot of details. You can write the code, in PySpark or in Scala, which is a big advantage, it is only easy to use for a developer. It will be difficult for new users to enter the cloud environment.

If business users want to run their own graphs they will not have the opportunity to use such features, such as running code inside AWS Glue in Spark, which will be complex for them.

 I have been using AWS Glue for approximately four years.

AWS Glue is a highly stable solution. We didn't have bugs in production. 

The solution works well with Spark, which is a good framework for large volumes of data. It operates very well.

I rate the stability of AWS Glue a ten out of ten.

The scalability of AWS Glue is great. It was used for enterprise customers. We worked a lot with AWS Glue for International companies.

We have approximately 10 people using AWS Glue in my company.

I have to use the support from AWS Glue. The response time could improve.

I rate the support from AWS Glue a nine out of ten.

Positive

The initial setup of AWS Glue is very simple.

AWS Glue uses a pay-as-you-go approach which is helpful. The price of the overall solution is low and is a great advantage.

If I can compare AWS Glue to other solutions, it has the advantage of the cloud, which assures availability and scalability, and the pay-as-you-go is beneficial. This is why many companies are moving from their traditional ETL tools to the cloud because the costs will be reduced dramatically.

I would recommend this solution to others.

I rate AWS Glue a nine out of ten.

We are using AWS Glue for transforming firewalls synced to the Data Lake in the bronze zone. The ATL uses the solution to transform fields in the silver layer and later we will produce the gold zone. We are using the Delta Lake Architecture.

The most valuable feature of AWS Glue is its ease of use and good documentation. Additionally, we can do all the transformations that we need.

The price of the solution could improve.

I have been using AWS Glue for approximately one month.

The stability of AWS Glue is good.

AWS Glue is highly scalable.

There are dozens of customers using this solution.

I have not used the support from AWS Glue but I know their support is good.

I have previously used Azure and Spark for testing.

The initial setup of AWS Glue is simple. In other solutions, such as Spark, the configuration would take a lot longer.

I did the deployment of AWS Glue myself with the AMS console. I am a data engineer.

The overall cost of AWS Glue could be better. It cost approximately $1,000 a month. There is paid support available from AWS Glue.

If the cost of AWS Glue was 50 percent less then we would not move to another solution.

I am moving to the EMR serverless or GCP solution.

I rate AWS Glue a nine out of ten.

We are primarily using it for batch crossing and transformations.

We have a large set of data and we are doing some transformations and identification. We are cleaning the data and transformations. Then we are putting the data into the destination table. So it is very comfortable.

The most valuable features currently are glue studio, jobs, and triggers.

I would like to see stable libraries at the moment they are not there.

I have been using AWS Glue for the past five years.

The stability I would consider to be an extensible Apache Spark.

The scalability is good and we have three hundred projects we are working with.

Previously, we used EMR, Informatica, Data Pipeline, and Azure Data Factory.

The initial setup is straightforward.

We did our deployment in-house with the CI/CD integrations like GitHub and deployed the code on Glue. 

We are seeing a very good return on our investment.

The current cost is around forty to fifty thousand a month.

I would definitely recommend using AWS Glue for batching procedures. I would rate AWS Glue an eight out of ten.

We used AWS Glue to build our data warehouse. We built prototypes to go all the way all across their warehouse platforms. From AWS Glue to Spreadsheets and then QuickSight, that's how we're building their warehouse.

I like that it's flexible, powerful, and allows you to write your own queries and scripts to get the needed transformations.

It would be better if it were more user-friendly. The interesting thing we found is that it was a little strange at the beginning. The way Glue works is not very straightforward. After trying different things, for example, we used just the console to create jobs. Then we realized that things were not working as expected. After researching and learning more, we realized that even though the console creates the script for the ETL processes, you need to modify or write your own script in Spark to do everything you want it to do.

For example, we are pulling data from our source database and our application database, which is in Aurora. From there, we are doing the ETL to transform the data and write the results into Redshift. But what was surprising is that it's almost like whatever you want to do, you can do it with Glue because you have the option to put together your own script. Even though there are many functionalities and many connections, you have the opportunity to write your own queries to do whatever transformations you need to do.

It's a little deceiving that some options are supposed to work in a certain way when you set them up in the console, but then they are not exactly working the right way or not as expected. It would be better if they provided more examples and more documentation on options.

I have been using AWS Glue since last year.

On a scale from one to ten, I would give AWS Glue a nine.

We use the solution to collect customers' data containing multiple files and convert it into a common database. Later, we send the database for SQL injection.

The solution's most valuable feature is its ability to efficiently collect and catalog the data in the warehouse.

They should improve the solution's performance in case of large amounts of data. Currently, AWS fails to handle massive databases acquired from various sources. Also, it is challenging to queue the data or use a standard code in AWS environment. We need to install a third-party tool to tackle the issue. We need to use another tool to convert the data as well. Thus, we are using multiple tools to handle the database. They should work on this particular area.

We have been using the solution for one year.

It is a stable solution. I rate its stability as an eight.

I rate the solution's scalability as a six.

The initial setup is a bit complex, and I rate the process as a six. We have to install multiple third-party tools whenever we update the security patches or renew the solution. Thus, the deployment process is complicated.

If you already have AWS environment, you can opt for AWS Glue for its ETL operations feature; if you want to process multiple operations, such as creating a table or catalog, or for machine learning purposes better to go for other database tools.

I rate the solution as a seven.

Our primary use case is ETL.

We have found it beneficial when moving data from one source to another.

The most valuable feature In terms of convenience, the drag-and-drop is really nice. The no-code interface, is really nice, being able to drag in my connectors. And then the nice thing, as well, is that it generates the framework, the wireframe of your code, so then you can just input whatever Spark or Python you want to input to make any further transformations.

I would like to see in general, documentation, on the limitations on which loads you can actually pull in when you are running Python. The additional Python Jupyter Notebook now has been nice. But yeah, generally speaking, you can not import every LOB. You can import branders now and you can use photos, but you can not import a lot of the other sorts of statistical-based loads. That is an issue currently. I would like to see a more robust interface on the no-code side. This would be nice to be able to split cells.

I have been using AWS Glue for the past three years.

The stability is excellent.

There is good scalability you can set up your minimum and maximum users and you are ready to implement.

The initial setup is straightforward If you are just doing a file format conversion, then it is very simple, but if you want to do a little bit more robust sort of transformations, like inserting transformations or you want to do transformations on multiple delimiters, then there is a bit of learning curve. The deployment time is literally minutes.

I would rate AWS Glue a seven on a scale of one to ten.

Our company uses the solution for ETL data movement for our customers such as on-premises to cloud, cloud to cloud, and cloud to Snowflake. We also data catalog and schedule ETL jobs. We are able to monitor all jobs through AWS services. 

Transformations are valuable because you can modify or override complex data logic from an open source or Spark to solve issues. 

For example, it is easy to solve issues where volume is good but performance is degrading because you can split jobs into small chunks to more quickly handle data loads. 

The setup and installation is a bit complex without advanced knowledge or training. It would be easier for an AWS expert or someone in DevOps.

Transformations need improvements to be more user friendly and rely less on coding like Matillion. 

I have been using the solution for three years. 

The solution's stability is decent and rates higher than other products. It works well with Snowflake, Azure, GCP, and AWS-supported products. 

A hybrid situation may cause delays in performance. 

The solution is scalable. 

One of our customers used technical support and found them to be helpful. 

The setup and installation is a bit complex. Training or advance knowledge is required. Someone with AWS experience or a DevOps perspective would have fewer issues. 

We install the solution for customers and the timeline depends on the job. 

A complete project will take a few days to a week for deployment. The number of jobs and components determines how many technicians are required for setup, installation, and deployment. Technician requirements can range from two to fifteen. 

Deployment will take a couple of hours for a few announcement jobs that deploy from the CI/CD pipeline.

The solution is my second choice because I prefer Snowflake's capabilities.