Scality RING Reviews

The most valuable feature of Scality RING8 is its performance and good interface.

Scality RING8 could improve by having more features. We have to use two automation tools to meet our needs. We would prefer to use only one.

I have been using Scality RING8 for approximately three years.

Scality RING8 is a stable solution.

The scalability of Scality RING8 is good. We are able to add subsets.

Our customers are enterprise-sized companies. The amount of people using the solution depends on the company's administration. However, they are using SAN and NAS and could have more than 100 people working on the solution.

The support from Scality RING8 is good.

I did not use another solution prior to Scality RING8.

The initial setup of Scality RING8 is complex. There are many commands and scripts that need to be launched. If you want to do the implementation yourself there are training sessions available.

There is a lot of documentation for the implementation.

We did not implement the solution ourselves, we used assistance.

The cost of Scality RING8 could be less expensive. It is difficult for smaller businesses to afford it.

I rate Scality RING8 an eight out of ten.

We used Scality during the capacity extension.

I think it's the economic factor. This solution has the lowest cost for storage systems.

If I had to choose a new aspect for the system, it would be the rebalancing. The ease of use during capacity upgrades would be the most important improvement. I don't know if they manage it better right now or not, but it was really horrible to extend capacity on Scality at the time that I used it.

When you add new servers in the node or ring, Scality does rebalancing to split the workload across all the nodes and servers. It moves the data from one server to another.

I did a backup for someone else, so I only have one month of experience with Scality. I did the project though and from there I just followed up with the associate or management of the project.

This solution is stability. 

When we used this solution in 2015, it was not scalable at all. I don't know if they have improved on that, but at the time, scalability was just horrible.

It's used within Orange in France, which handles petabytes of data. I don't know exactly how much it was, but I think we are talking about five, or even more than that. When I worked on this project, it was during migration. It is definitely getting higher and higher in terms of capacity that you can use.

Scality's technical support team is good.

I'm starting to work on a project now with ScaleIO. The engineering team suggests migrating to Red Hat Ceph. I don't know yet what their reasons are, but that was the information I got two weeks ago. I am now starting to look for information comparing the products. For the project I'm working on now, we need block storage, so Scality is not an option in this case. Scality is used for object storage and here we are talking about another solution for block storage. Today we are using ScaleIO, which engineering recommends. It's a common thing to migrate to Red Hat Ceph.

My experience in 2015 was that it was not easy. Each time we needed to get the Scality professional services to help us at that time.

I think I would recommend Scality but there is another solution that I'm going to dig into more, which is OpenIO. Right now for new projects, I don't know yet if I'm going to recommend Scality or OpenIO. Most probably OpenIO, but it's not necessarily based on technical features. It's because we have a commercial agreement with OpenIO.

I would rate this solution as eight out of ten.

S3 and CDMI, restful API for object access, are useful for deploying standard S3 or CDMI-based applications such as cloud backup, email.

Erasure coding technologies permit to reduce storage costs by providing the same security as replication but with less storage resources.

Scality permit to deploy a data/metadata ring on 2 sites, a specific DRP ring on a remote site.

Each ring can have its own QoS (Rep3, EC,…) in order to provide application-based SLAs

We have benefitted from cloud storage adoption.

S3 complete compliance which is planned for v6.

I have used this solution for five years.

Only at the beginning because of a specific implementation issue.

Adding a storage node is simple but rebalancing takes a long time (several weeks).

The technical support is correct.

Scality is the first cloud storage product we have used.

The setup was complex.

This product is interesting if you target a least 10 PB.

We evaluated SwiftStack, Cleversafe, HDS Content Platform, and Mezeo.

Take care of S3 compliance and metadata ring architecture.