How does Utilihive compare to Cloudera as a data platform?

Cloudera Enterprise is well suited for organizations that want to build their own Enterprise Big Data Hub from the ground up and perform data analysis on it. Cloudera Enterprise is a horizontal platform using open-source Cloudera Distribution of Hadoop (CDH). For clients it means allocating additional resources to manually build, integrate, operate, and manage another additional data lake infrastructure such as Hadoop, Elastic, time series data, etc. with data integration. Cloudera typically uses Kafka as a software bus. Apache Kafka is a horizontal messaging / streaming platform. As Apache Kafka is purely the messaging / streaming platform the client would have to do significant integration work that would integrate specific use cases being built.


Utilihive
is a full-fledged data integration hub combining data integration and data lake capabilities (plus an API Gateway to secure data access) into one unified platform and experience. Utilihive is purpose-built for Utilities with pre-built accelerators that accelerate time to value which clients would otherwise have to build and manage themselves.

  1. Utilihive combines data integration / data ingestion capabilities and data lake capabilities into one platform with one unified management environment. Compared to Cloudera with Kafka, one would have to build a data lake infrastructure in addition meaning that clients would be responsible for building, integrating, and managing Kafka and Hadoop.
  2. Utilihive has preconfigured connectivity with Apache Kafka, Apache Pulsar, mqtt and many other technologies. Utilihive supports both batch style integration and the kind of Kafka-style streaming integration. With Cloudera, clients would have to build, integrate, and manage an own / additional infrastructure for non-streaming data types.
  3. Utilihive utilizes and incorporates the Common Information Model (CIM) data model. Cloudera requires clients to develop and maintain the data model.
  4. Utilihive offers a pre-configured data lake / data mesh implementation for energy and utility use case with commonly used data structures including time series data, geospatial information, asset data, events, alarms providing unified data ingestion and data retrieval services across those different storage technologies needed. Cloudera, requires users to implement, maintain, and operate the implementation of the data lake application.
  5. Utilihive exposes managed and therefore secured data services APIs on its built-in API Gateway controlling all access to data. Cloudera requires clients to build, integrate, and manage an additional component to act as an API Gateway.
  6. Utilihive has pre-configured integration with commonly used utility applications including most suppliers offering HES, MDM, CC&B, GIS, Asset Management, SCADA and more. Comparing this to Cloudera, clients would have to develop and maintain those “connectors” over time. 
  7. Utilihive supports hybrid deployments where both integrations and data buckets can be operated and distributed between on-premise, private cloud or public cloud. Cloudera requires clients to implement and maintain this “distributed data architecture.”

Related stories