Zenko engineering team has been working for almost two years on the open source code that allows developers to keep control of their data while gaining freedom to choose the best storage options. You’re not forced to pick among Amazon S3, Azure Blob Storage, Google Cloud Storage but you can have them all with Zenko!
ICYMI, watch the recording below to learn why CIOs and data managers love Zenko:
- Stores all data unmodified so that it can be accessed and acted on in the cloud directly.
- Enables data mobility so that data can be easily placed in the most efficient location.
- Provides a single endpoint through which data can be stored, retrieved and searched across any location.
- Enables unified data management from anywhere through a secure cloud portal.
- Can be deployed using Kubernetes orchestration framework.
Questions from the webinar:
Q. Does Zenko have any plans to integrate with decentralized cloud storage layers?
A. Zenko’s plan is to support as many storage backends as possible and that includes decentralized cloud storage. More specifically, we partnered with Storj and are working to integrate Zenko with their next-generation network.
Q. What is the Orbit website?
A. Orbit is Zenko’s configuration and management interface. Offered as a SaaS graphical interface, it can connect to Zenko instances deployed on-premises or in the cloud. Orbit also offers the possibility to get a free Zenko sandbox to quickly test the capabilities of the system
Q. Does Zenko have its own meta repository to track key/value (metadata) on objects?
A. Object’s metadata are stored in MongoDb inside Zenko cluster and natively stored with the object in each cloud destination.
Q. We’re have a large enterprise class object store with over 10+ PB of data in over 1000 buckets. It’s all internal facing (internal applications/developers/archives, etc). Would Zenko sit in front of this object store (become the primary S3 endpoint) for all apps/consumers using our object store?
A. Zenko can be in front or on the side, depending on the needs of users. Depending on the features of the existing object store, applications can keep on using the existing store while Zenko gets notified out-of-band of updates in the content of buckets, for example.
Q. Can zenko be used to migrate data between clouds
For existing data, you have to tell Zenko that the data exists. Once the out-of-band updates features is complete, migrations of data can be made automatic.
Q. Does Zenko have its own lifecycle (expiration for example) of objects? Example would be our own back-end object store does not have expiration. Would Zenko be able to delete the object upon expiration?
A. Yes, Zenko can augment the features of an existing object store and we’re seeing requests related to Ceph, which doesn’t have native cloud replication or expiration policies.
Q. Can Zenko keep up with a high request rate s3 customer? (such as 100+ new objects per second)
A. Zenko can handle millions of requests per second, it’s well tested with Cloudserver.
Q. Is there support for IBM Cloud Object Storage (back-end) on prem ; or public?
A. Since IBM Cloud Object Storage is compatible with S3 APIs the integration is quite simple, it requires simple code like we’ve done with Wasabi or Digital Ocean Spaces.
Q. If I connect my instance to Orbit and later disconnect it, what happens to my data and metadata?
A. Orbit is only a configuration and management tool. The metadata is stored inside the Zenko instance in a distributed MongoDB database. Once Orbit is detached, Zenko will continue to operate as usual.
If you have more thoughts and questions, post on the forums (and in the comments section below –same thing)!