Azure Data Lake Storage vs. IBM Analytics Engine

Azure Data Lake is an absolutely essential piece of a modern data and analytics platform. Over the past 2 years, our usage of Azure Data Lake as a reporting source has continued to grow and far exceeds more traditional sources like MS SQL, Oracle, etc.

Incentivized

• Well suited for my big data related project or a static data set analysis especially for uploading huge dataset to the cluster.
• But had some issues with connecting IoT real-time data and feeding to Power BI. It might be my understanding please take it as a mere comment rather than a suggestion.

Incentivized

• Setting up Azure Data Lake Storage account, container is quite easy
• Access from anywhere and easy maintenance
• Integration with Azure Data Factory service for end to end pipeline is pretty easy
• Can store Any form of data (Structured, Unstructured, Semi) in faster manner

Incentivized

• Jobs with Spark, Hadoop, or Hive queries are rapidly attained
• Can collect, organize and analyze your data accurately
• You can customize, for example, Spark or Hadoop configuration settings, or Python, R, Scala, or Java libraries.

Incentivized

• study for the certifications also to have them as a reference for work when you have any questions about applying a configuration to the equipment.
• The Internet interface is simple and easy to use. Capacity is good and it's good that HP continues to innovate with this technology

Incentivized

• Easier pricing and plug-and-play like you see with AWS and Azure, it would be nice from a budgeting and billing standpoint, as well as better support for the administration.
• Bundling of the Cloud Object Storage should be included with the Analytics Engine.
• The inability to add your own Hadoop stack components has made some transfers a little more complex.

Incentivized

Azure Data Lake Storage from a functionality perspective is a much easier solution to work with. It's implementation from Amazon EMR went smooth, and continued usage is definitely better. However, Amazon EMR was significantly cheaper overall between the high transaction fees and cost of storage due to growth. The two both have their advantages and disadvantages, but the functionality of Azure Data Lake Storage outweighed it's cost

Incentivized

We initially wanted to go with Google BigQuery, mainly for the name recognition. However, the pricing and support structure led us to seek alternatives, which pointed us to IBM. Apache Spark was also in the running, but here IBM's domination in the industry made the choice a no-brainer. As previously stated, the support received was not quite what we expected, but was adequate.

Incentivized

• Instead of having separate pools of storage for data we are now operating on a single layer platform which has cut down on time spent on maintaining those separate pools.
• We have had more of an ROI with the scalability as we are able to control costs of storage when need be.
• We are able to operate in a more streamlined approach as we are able to stay within the Azure suite of products and integrate seamlessly with the rest of the applications in our cloud-based infrastructure

Incentivized

• This product has allowed us to gather analytics data across multiple platforms so we can view and analyze the data from different workflows, all in one place.
• IBM Analytics has allowed us to scale on demand which allows us to capture more and more data, thus increasing our ROI.
• The convenience of the ability to access and administer the product via multiple interfaces has allowed our administrators to ensure that the application is making a positive ROI for our business users and partners.

Incentivized