Apache Pig is best suited for ETL-based data processes. It is good in performance in handling and analyzing a large amount of data. it gives faster results than any other similar tool. It is easy to implement and any user with some initial training or some prior SQL knowledge can work on it. Apache Pig is proud to have a large community base globally.
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
Iterative Development - you can write aliases/variables, which are not immediately executed and these are stored in a DAG, which is only evaluated upon dumping or storing another alias.
Fast execution - Works with MapReduce, Tez, or Spark execution frameworks to provide fast run times at large scales.
Local and remote interoperability - Scripts that depend on testing a small dataset locally before moving to the full thing can simply be done with "pig -x local."
It takes me less time to write a Pig script than get a Spark program running for batch ETL workloads. Compared to Spark, Pig has a steeper learning curve because it employs a proprietary programming language. In one script and one fine, it can handle both Map Reduce and Hadoop. It has a large amount of documentation available to make learning more convenient.
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
Return on Investments are significant considering what it can do with traditional analysis techniques. But, other alternatives like Apache Spark, Hive being more efficient, it is hard to stick to Apache Pig.
It can handle large datasets pretty easily compared to SQL. But, again, alternatives are more efficient.
While working on unstructured, decentralized dataset, Pig is highly beneficial, as it is not a complete deviation from SQL, but it does not take you in complexity MapReduce as well.
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.
