Harbor vs Cloudflow: What are the differences?

Harbor: Manage and serve container images in a secure environment (created at VMware). Harbor is an open source cloud native registry that stores, signs, and scans container images for vulnerabilities Harbor solves common challenges by delivering trust, compliance, performance, and interoperability. It fills a gap for organ; Cloudflow: *Streaming Data Pipeline on Kubernetes *. It enables you to quickly develop, orchestrate, and operate distributed streaming applications on Kubernetes. With Cloudflow, streaming applications are comprised of small composable components wired together with schema-based contracts. It can dramatically accelerate streaming application development—​reducing the time required to create, package, and deploy—​from weeks to hours.

Harbor belongs to "Docker Registry" category of the tech stack, while Cloudflow can be primarily classified under "Big Data Tools".

Some of the features offered by Harbor are:

• Multi-tenant content signing and validation
• Image replication between instances
• Extensible API and graphical UI

On the other hand, Cloudflow provides the following key features:

• Apache Spark, Apache Flink, and Akka Streams
• Focus only on business logic, leave the boilerplate to us
• We provide all the tooling for going from business logic to a deployable Docker image

Harbor and Cloudflow are both open source tools. Harbor with 11.5K GitHub stars and 3.13K forks on GitHub appears to be more popular than Cloudflow with 172 GitHub stars and 50 GitHub forks.