Sqoop is great for sending data between a JDBC compliant database and a Hadoop environment. Sqoop is built for those who need a few simple CLI options to import a selection of database tables into Hadoop, do large dataset analysis that could not commonly be done with that database system due to resource constraints, then export the results back into that database (or another). Sqoop falls short when there needs to be some extra, customized processing between database extract, and Hadoop loading, in which case Apache Spark's JDBC utilities might be preferred
We are at present utilizing IBM Analytics Engine and it works incredible. Following are the things that I like the most about this product is:- - Simple to Utilize - Reasonable Cost - With only a couple seconds you can ready to fabricate and convey groups - you can without much of a stretch break down information through different applications
Sqoop2 development seems to have stalled. I have set it up outside of a Cloudera CDH installation, and I actually prefer it's "Sqoop Server" model better than just the CLI client version that is Sqoop1. This works especially well in a microservices environment, where there would be only one place to maintain the JDBC drivers to use for Sqoop.
Sqoop comes preinstalled on the major Hadoop vendor distributions as the recommended product to import data from relational databases. The ability to extend it with additional JDBC drivers makes it very flexible for the environment it is installed within.
Spark also has a useful JDBC reader, and can manipulate data in more ways than Sqoop, and also upload to many other systems than just Hadoop.
Kafka Connect JDBC is more for streaming database updates using tools such as Oracle GoldenGate or Debezium.
Streamsets and Apache NiFi both provide a more "flow based programming" approach to graphically laying out connectors between various systems, including JDBC and Hadoop.
I have been using Azure for my previous analysis, I had a difficult time in understanding the Analytics engine rather IBM provided step by step tutorial for setup.
Also turning off a machine was not an option in Azure for some of the services so I had to pay for the service whether I use it or not
When combined with Cloudera's HUE, it can enable non-technical users to easily import relational data into Hadoop.
Being able to manipulate large datasets in Hadoop, and them load them into a type of "materialized view" in an external database system has yielded great insights into the Hadoop datalake without continuously running large batch jobs.
Sqoop isn't very user-friendly for those uncomfortable with a CLI.
It has saved us quite a bit of time managing our catalog of clusters and keeping things organized.
Since we had a division we acquired running IBM Cloud, it was easy to get it running and try it out, but we found we prefer our Azure configuration better simply to keep our technology in alignment across corporate functions.
I definitely see some cost savings by separating out the storage and compute. It helps you start to put an appropriate price tag on certain instances of big data.
