Cloudera Enterprise Data Hub vs. CloudFoundry

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.

Incentivized

It's well suited if:

• The organization has large number of applications that needs to be deployed frequently.
• The organization is tied to the DevOps mindset.
• The organization has programs in different languages.
• The applications does not need EJB's support that servers like web logic provide.

It's less suited if:

• The applications needs security configuration within the same CloudFoundry instance.
• The organization, for whatever reason does not want developers to manage the instances.

Incentivized

• Excellent management capabilities via Cloudera Manager.
• Open source and does not restrict our data to be bound by a proprietary format.
• Offers excellent support for data governance and auditing.
• Has all the components that would help us build a data hub.
• Excellent platform support offered by Cloudera.

• Support for Orgs and Spaces that allow for managing users and deployables within a large organization.
• Easy deployment, deploying code is as simple as executing single line from CLI, thanks to build-packs.
• Solid and rich CLI, that allows for various operations on the instance.
• Isolated Virtual Machines called Droplets, that provide clean run time environment for the code. This used to be a problem with Weblogic and other application servers, where multiple applications are run on the same cluster and they share resources.
• SSH capability for the droplet (isolated VM's are called droplets), that allows for real time viewing of the App code while the application is running.
• Support for multiple languages, thanks to build-packs.
• Support for horizontal scaling, scaling an instance horizontally is a breeze.
• Support for configuring environment variable using the service bindings.
• Supports memory and disk space limit allocation for individual applications.
• Supports API's as well as workers (processes without endpoints)
• Supports blue-green deployment with minimal down time

Incentivized

• Not fully Open Source, couple of components of the distributions are privately owned, meaning with public contributions are not welcome
• Improvements to Cloudera manager can only be recommended. its very hard to get it done once recommended as the full control is with them.
• Should make components more aligned to Open Source rather than making it closed sourced.
• Custom Features of open source software tools supported only by Cloudera are tricky. Cant commit changes to tools like Hue.
• Improvements to Cluster Management tool is required, which are already available to its competitors.

Incentivized

• Does not support stateful containers and that would be a nice to have.
• Supports showing logs, but does not persist the logs anywhere. This makes relying on Cloud Foundry's logs very unreliable. The logs have to be persisted using other third party tools like Elk and Kibana.

Incentivized

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.

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.

Incentivized

While Docker shines in providing support for volumes and stateful instances, Cloud foundry shines in providing support for deploying stateless services. Heroku shines in integrating with Git and using commits to git as hooks to trigger deployments right from the command line. But it does not provide on-premise solution that Cloud foundry provides.

Incentivized

• 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.

• Positive impact, since it simplifies the deployment time by a huge margin. Without cloud foundry, deploying a code needs coordination with infrastructure teams, while with cloud foundry, its a simple one line command. This reduces the deployment time from at least few hours to few minutes. Faster deployments promote faster dev cycle iterations.
• Code maintenance such as upgrading a Node or Java version is as simple as updating the build-pack. Without cloud foundry, using web logic, the specific version only supports a specific version of Java. So updating the version involves upgrading the version of web logic that needs to involve few teams. So without cloud foundry, it takes at least few days, with cloud foundry, its a matter of few mins.
• Overall, happier Developers and thats harder to quantify.

Incentivized