The Cloudera Enterprise Data Hub powered by SDX is a multifunction analytics solution that supports a range of operational and analytic use cases for enterprises.
N/A
Qubole
Score 5.2 out of 10
N/A
Qubole is a NoSQL database offering from the California-based company of the same name.
Cloudera excels at seamless migrations and upgrades.
Cloudera supports self-healing and data center replacement of failed cloud instances while maintaining the state.
Cloudera is essential to increase or decrease capacity through the user interface or API.
Cloudera is great at simplifying big data analytics by providing the technology and tools needed to gain insights from IoT and connected devices to help monitor and condition our assets.
Cloudera's cybersecurity platform option offers stronger anomaly detection, visibility, and prevention, as well as faster behavioral analysis.
Cloudera is beneficial for enabling and utilizing the platform's machine learning and ad-hoc queries while securely storing, retrieving, and analyzing any volume of data at scale.
I find Qubole is well suited for getting started analyzing data in the cloud without being locked in to a specific cloud vendor's tooling other than the underlying filesystem. Since the data itself is not isolated to any Qubole cluster, it can be easily be collected back into a cloud-vendor's specific tools for further analysis, therefore I find it complementary to any offerings such as Amazon EMR or Google DataProc.
Providing an open selection of all cloud provider instance types with no explanation as to their ideal use cases causes too much confusion for new users setting up a new cluster. For example, not everyone knows that Amazon's R or X-series models are memory optimized, while the C and M-series are for general computation.
I would like to see more ETL tools provided other than DistCP that allow one to move data between Hadoop Filesystems.
From the cluster administration side, onboarding of new users for large companies seems troublesome, especially when trying to create individual cluster per team within the company. Having the ability to debug and share code/queries between users of other teams / clusters should also be possible.
Likely to renew the use in case the requirements for Cloudera remain valid. The rapid change in customer requirements and solutions that must be validated, integrated or tested changes. As the maturity of the solution increases, the requirements to renew use decrease. From a solution feature perspective by itself would probably grade 10.
Personally, I have no issues using Amazon EMR with Hue and Zeppelin, for example, for data science and exploratory analysis. The benefits to using Qubole are that it offers additional tooling that may not be available in other cloud providers without manual installation and also offers auto-terminating instances and scaling groups.
Cloudera is compatible with Windows operating systems, and Mac allows cloud-based deployment, it is also very useful to configure data encryption, guarantee protocols, and security policies. It also provides integrated auditing and monitoring capabilities, as well as a control comprehensive data repository for the enterprise, and ensures vendor compatibility through its open-source architecture.
Qubole was decided on by upper management rather than these competitive offerings. I find that Databricks has a better Spark offering compared to Qubole's Zeppelin notebooks.
Cloudera products are the most widely. It is more business friendly as data is more secure. The sensitive data that you operate on is local to you and your project rather than processing this data on Cloud.
Cloudera is definitely faster as wait time is reduced if on Cloud.
A lot range of products are covered. So it is definitely good for businesses and had good returns on investments.
We like to say that Qubole has allowed for "data democratization", meaning that each team is responsible for their own set of tooling and use cases rather than being limited by versions established by products such as Hortonworks HDP or Cloudera CDH
One negative impact is that users have over-provisioned clusters without realizing it, and end up paying for it. When setting up a new cluster, there are too many choices to pick from, and data scientists may not understand the instance types or hardware specs for the datasets they need to operate on.
