Average Ratings 0 Ratings
Average Ratings 0 Ratings
Description
IPFS Cluster enhances data management across a collection of IPFS daemons by managing the allocation, replication, and monitoring of a comprehensive pinset that spans multiple peers. While IPFS empowers users with content-addressed storage capabilities, the concept of a permanent web necessitates a solution for data redundancy and availability that preserves the decentralized essence of the IPFS Network. Serving as a complementary application to IPFS peers, IPFS Cluster maintains a unified cluster pinset and intelligently assigns its components to various IPFS peers. The peers in the Cluster create a distributed network that keeps an organized, replicated, and conflict-free inventory of pins. Users can directly ingest IPFS content to multiple daemons simultaneously, enhancing efficiency. Additionally, each peer in the Cluster offers an IPFS proxy API that executes cluster functions while mimicking the behavior of the IPFS daemon's API seamlessly. Written in Go, the Cluster peers can be launched and managed programmatically, making it easier to integrate into existing workflows. This capability empowers developers to leverage the full potential of decentralized storage solutions effectively.
Description
As the utilization of Kubernetes continues to increase, organizations are discovering the necessity of managing and deploying several clusters in order to support essential capabilities such as geo-redundancy, scalability, and fault isolation for their applications. Submariner enables your applications and services to operate seamlessly across various cloud providers, data centers, and geographical regions. To initiate this process, the Broker must be set up on a singular Kubernetes cluster. It is essential that the API server of this cluster is accessible to all other Kubernetes clusters that are linked through Submariner. This can either be a dedicated cluster or one of the already connected clusters. Once Submariner is installed on a cluster equipped with the appropriate credentials for the Broker, it facilitates the exchange of Cluster and Endpoint objects between clusters through mechanisms such as push, pull, and watching, thereby establishing connections and routes to other clusters. It's crucial that the worker node IP addresses on all connected clusters reside outside of the Pod and Service CIDR ranges. By ensuring these configurations, teams can maximize the benefits of multi-cluster setups.
API Access
Has API
Yes
API Access
Has API
Yes
Integrations
Docker
Yes
Ethereum
Yes
Filecoin
Yes
IPFS
Yes
Kubernetes
No
Netdata
Yes
Integrations
Docker
No
Ethereum
No
Filecoin
No
IPFS
No
Kubernetes
Yes
Netdata
No
Pricing Details
No price information available.
Free Trial
No
Free Version
No
Pricing Details
No price information available.
Free Trial
No
Free Version
No
Deployment
Web-Based
Yes
On-Premises
No
iPhone App
No
iPad App
No
Android App
No
Windows
No
Mac
No
Linux
No
Chromebook
No
Deployment
Web-Based
Yes
On-Premises
No
iPhone App
No
iPad App
No
Android App
No
Windows
No
Mac
No
Linux
No
Chromebook
No
Customer Support
Business Hours
No
Live Rep (24/7)
No
Online Support
Yes
Customer Support
Business Hours
No
Live Rep (24/7)
No
Online Support
Yes
Types of Training
Training Docs
Yes
Webinars
No
Live Training (Online)
No
In Person
No
Types of Training
Training Docs
Yes
Webinars
No
Live Training (Online)
No
In Person
No
Vendor Details
Company Name
IPFS Cluster
Website
cluster.ipfs.io
Vendor Details
Company Name
Submariner
Website
submariner.io