Think of ETL: Think AWS GLUE
Use Cases and Deployment Scope
We have certain transformations needs, we use Glue to fulfil them. As its integrated service from AWS itself, the connectivity to other AWS service is pretty seamless. As it’s fully serverless, we don’t have to worry about the infrastructure as well. It can crawl the things for us so we don’t have worry about the updation in our source, we got to know itself. So it’s powerful ETL FOR US.
Pros
- Scale up and scale down easily
- Seamless connectivity with other AWS services
- Cost effective as you need to pay what you are using.
Cons
- 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
Likelihood to Recommend
To integrate within AWS services, it’s great ETL tool which can work perfectly with our S3 buckets and SQL DB.
but when it comes to integrate it with Multi cloud infrastructure, its connectivity and compatibility lacks, i.e. if we have to connect to IBM cloud objects, it’s not possible in any way to have our data source being in other cloud vendor.