It easily scales. We have about 500 users with the majority being software and systems engineers.

We are at a half of one petabyte range. We do find that data can be ingested and accessed a fast rate.

If you were to do gigabyte per person, we can store more data per person than we used to with traditional storage by at least 200 percent.

The scalability has been fantastic.

We are not quite at the petabyte range yet. We're just barely under one petabyte. The ingestion is not an issue. Thus far, because it's primarily a backup target, the ingest has been fine. We haven't had any significant restores that need to be done. The general consensus on what we've done is that the restores coming back from it have been faster than they were from our prior vendor. Ingest speeds are fine. The restore speeds have improved.

It is backing up enterprise systems in our data center. Those enterprise systems are being used by close to 600 staff, both administrative and scientific. That staff doesn't directly interact with SwiftStack, but the data that they store is on our primary storage system and gets backed up to it. Indirectly, they're being covered by the capacity on the SwiftStack system.

We are kicking the tires on the SwiftStack 1space feature right now. We're trying to determine the namespace that we'd want to use. Because we're in a transitional period, we're looking at increasing our capacity. We're going to bring on two new SwiftStack nodes with additional capacities. Part of that will be the 1space with the ability to move out to Azure and AWS, who right now are our two primary cloud providers. However, GCP will also likely be involved. Therefore, we're in the process of formulating a long-term plan that won't require us to re-architect after we get out and running.

Our use case for the 1space feature is cold archives and the ability to move some of the data out of our on-premise data centers because of federal mandates for data center consolidation initiatives. It puts more emphasis on shrinking space in the data center, which means denser, greater storage capacity on-premise, but then some of that data needs to move out to the cloud.

The possibility is also there for doing some bursting to the cloud for a cloud compute. This is a future desire that we would like to look into, though it is not on our official roadmap. The transition to public cloud hasn't even been tied in yet.

Going forward, we will be adding two nodes. We are still waiting on the hard drives. Once they are added, we will be expanding our capacity by 70 percent.

As far as I'm concerned, the scalability is endless. Scalability is not an issue. I don't even think about it. If I need capacity, I purchase the stack license, purchase my hardware, and off we go.

We found scalability to be good. The platform is capable of scaling to very large capacities. Overall, manageability at scale is pretty good. There are areas that they are continuing to improve, like code upgrades, which are needed to take it to super large scale. However, compared to most solutions, scalability is pretty high for very large multitenant capacity requirements.

We maintain the platform with less than five people. They predominantly are just cloud engineers. This doesn't count people who touch the platform peripherally, like network engineers.

Our customers' users number in the hundreds.

We have about 35 servers in our environment today. We are getting ready to go to between 40 and 50 servers in our environment.

Up until now, we have not encountered any scalability issues.

As we go, there are more and more people interested. It's steadily growing. In the Netherlands, there is an organization called NWO which is similar to the National Science Foundation. The NWO has departments that are all about research and data management, and they have a solution for that. They are also interested in using SwiftStack as a storage backup.

We have between 50 and 60 SwiftStack users. Because we are an academic computer center providing services to universities, a lot of those people are not within our company, but are working at universities. There are researchers, professors, etc. Within our company, Surfsara itself is mainly used for backups. Those are accounts that are not really attached to people but which are attached to a service.

It is very easy to scale. Installing SwiftStack on every node is easy.

Its users include me and my backup. I need to support it every day, but I don't use it every day. 

The developers use the SwiftStack Client to connect to the storage, which is also easy to deploy. Our main purpose as an organization is to provide archived documents. They're testing the platform every day. I'm assuming that in one way or another, they use it every week.

The scalability is phenomenal. It seems infinite, as long as you put enough storage in place, add enough nodes. We've scale-tested it in Amazon to meet any kind of needs we want, as long as we keep up with the hardware.

No issues encountered.