MinIO Reviews

I was using MinIO for my own research and some other work which I cannot disclose.

MinIO has brought more scalability, use of computing resources, and it can lead towards higher cost savings for companies.

The features that I have found most valuable with MinIO is its coding bit rot protection and how it distributes the workload over all the servers. I observed that the workload is very even in all the nodes.

I like the interface. It's beautifully designed and it's great. It's one of the best platforms I've seen and it is highly compatible. The only downside I see is that you do not have a complete picture of an object.

Additionally, a feature I would like to see in the next release would be if they can include an uneven disk structure. Then you can use an uneven number of disks and create a bunch of tickets by a factor of two. If I could use an odd number of disks, that would be better, it would give me more flexibility.

MinIO can sometimes crash because of the dependency in underlying OS software layers. Of course it crashes depending on the file system. There is a heavy dependence on the node's file system, that is another issue.

MinIO requires ongoing maintenance by the staff. Their interface is pretty good, it just needs a software upgrade.

MinIO should be easy to scale. It's an evenly scaling system.

I have plans to increase the usage.

The initial setup was simple.

You just need one person to do that part of the small cluster and I had a pretty small cluster so it didn't take much time - maybe half a day.

My advice to anyone considering using MinIO would be to first check if the open source version works for you. It probably should be able to. It has an S3 plugin so quite easily you can have interoperability between the public and private cloud or a hybrid setup. That is one advantage of the system. So if you need a private enterprise working as a public cloud, then MinIO is one of the best solutions I've seen so far.

I was using it for my personal work and MinIO it's a high-performance object storage system. So when you need high performance, you should go to MinIO.

On a scale of one to ten, I would rate MinIO an eight.

In the current market, when you have so many options for objects storage, MinIO is completely open source and an all inclusive package offering you both stability and scalability and its most attractive feature is the S3 plugin which is very similar to AWS.

Our primary use case of this solution is for the microservices architecture built with .NET Core. I'm a senior software engineer and we are customers of MinIO. 

The solution has provided the company with a super approach in development and testing environments which is what we were looking for. 

The solution has a good interface. We initially used several commands for configuring in the Docker Compose to create the default bucket and to make it public. It was pretty easy to use and fulfilled our requirements. It's quite powerful.

We had some issues with the initial configuration which I think could be improved by working on the documentation. I had to search different sources to get what I needed. 

The MinIO client was hard to automatize, we had to include some scripting on startup of the client container so that the buckets were setup with the read/write permissions and to make it public and accessible

I've been using this solution for two years. 

We haven't had any issues with stability. 

The way we deployed the test environment was to have just one instance for every container so every user was able to run their own test environment and we didn't need to scale. There were somewhere between 20 and 30 users, product owners and testers. The solution didn't require any maintenance. Expanding use will depend on the amount of information they have to store. 

In the test environment we were using Terraform scripts with the commands for the MinIO Client to set up the MinIO, and all the containers were deployed to a Nomad Ecosystem. We used the continuous deployment to deploy and create the test environments with Azure DevOps. There were three back end developers and two DevOps people that helped with deployment but I did most of it, configuring the continuous integration and deployment of the project. 

The most difficult part of the setup was to configure the MinIO Client, because I'm used to working with Windows and the Docker containers were running on a Linux container. I had to figure out the commands, create the bucket and make it public. It took a bit of research and documentation was an issue.

The solution was intended for private cloud, but we also had an on-premise installation which meant we could manually install the MinIO in every computer required. For on-premise installations, we could install MinIO and just change the connection string of the service using that MinIO. I recommend the solution, it's quite simple to implement and is very powerful because if you need to run the storage in your computer it's as simple as having a container of MinIO. 

I rate this solution eight out of 10. 

We used it for machine learning artifacts in terms of model weights and the model outputs for visualizations for ephemeral tasks.

I was using it less than a year ago, and it was the latest open-source version.

It helped us to use AWS because we wanted a hybrid solution or to move to AWS eventually. MinIO provided that bridge. We could write code only once and make it work with MinIO. When we move the same code to the cloud to scale it, it will still continue to work.

The ability to spawn a MinIO Tenant on demand and shut it down right after is most valuable.

There should be the ability to expand the size after it has already been deployed. Currently, you cannot do that. It doesn't support an increase in size. Each time we spawn a new MinIO, we need to track the particular MinIO instance or tenant that has the file. Therefore, we had to create a multi-tenant solution that tracks the MinIO that has our artifacts. It isn't in one single instance. It should have better multi-tenancy support.

On Kubernetes, it wasn't as stable as we wanted it to be.

It scales very well. It integrates quite well with other solutions.

We had probably a couple of hundred users. Their titles were Machine Learning Engineers or DevOps Engineers.

I didn't have to call up MinIO for tech support. There is documentation, but it is not so good.

We are phasing it off, and we are going to AWS. We have stopped using MinIO. At the moment, we are using Alluxio.

It was a bit complex. The complete deployment took about a month and a half.

We used Kubernetes YAML files because we were using MinIO on Kubernetes. Once that was up, we had to expose the MinIO instances via load balancers. That's how we connected MinIO.

In terms of maintenance, we have to make sure that we're always using the latest version. So, we have SRE people deployed to just monitor the health and versions. We have to update a few hundred instances of MinIO.

I would advise others to not use MinIO on Kubernetes. I would rate MinIO an eight out of 10.

I am using the solution for a POC. I am using MinIO to share volumes between different containers.

The most valuable feature of MinIO is its ease of use, replication, and active directory. All the capabilities are in this solution.

The documentation of the solution should improve.

I have been using MinIO for approximately one year.

The stability of MinIO is great.

We have approximately eight people using the solution.

The solution is scalable.

I have not used the support from the vendor. I have not had any problems.

The initial setup was simple. We had to download some samples and do the configuration. The process can be done quickly, but the full POC tool many months, and it can be complicated.

I did the deployment of two nodes.

We have done the POC and next will be the production, I recommend the solution.

I rate MinIO an eight out of ten.

We were trying to implement on object-storage a distributable solution and the main use was for cryptocurrency mining. The cryptocurrency uses block storage or different storage for crypto mining.

With MinIO, we managed to go forward with our cryptocurrency mining project. 

The ease of use, the low memory footprint, and the community is quite helpful as well. The web interface is also pretty nice.

At the time, they were rewriting their documentation and they had two versions of it: legacy. found at https://docs.min.io/, and the current, which has 3 versions at the time; one of them being: https://docs.min.io/minio/bare...

Some of the information was in one and some was in the other. There wasn't just one place to go and look for whatever you required. They still appear to have a warning on top of the "baremetal docs".

I've been using it for the last six months or so.

We've had a few crashes because of excessive use. We struggled a little to learn where the problem was. Everything was in containers and it sometimes made visibility hard to get to the logs so we could figure out exactly what the problem was. 

It seems to be pretty scalable because you just need to add more nodes for instances of MinIO and it connects automatically.

We did not use paid support, but the community communication channels, mainly Flat.

Positive

We were using OpenStack, Shift, and Keystone. They provided an optic-storage solution, but it's fairly complicated to install and to maintain and to upgrade. Performance wasn't great either because of our type of setup, so we decided to check MinIO out, and the managers liked it. We ended up implementing.

I deployed MinIO myself. Deployment is pretty easy and straightforward. The one thing that takes more time is the tuning because it's made to be very automatic, so you don't have to mess a lot with the configuration. But in the end, you need to tweak it. So, installation was easy. It took two hours, maybe less. Tuning probably took a few days.

We deployed it in-house. 

That is not my area, but I am sure it is high. The service works fine and the deployment cost was minimal.

We went with the open source version. I wouldn't know what to tell you about licensing. That said, I think the open source version is quite good and has everything one needs.

We were using OpenStack Swift at the time. It's kind of difficult to deploy and manage in standalone mode. Also, the performance isn't as good. 

I would rate this solution a nine out of ten.

There were two huge users, but at points, there were many sporadical users. So basically, the two users were consuming 80% or 90% of the resources, while the rest of the users, maybe ten of them, working just indirectly.

The premise required a bit of maintenance, which I was responsible for. They tried to update very often. In fact, every two weeks they tried to make a release or they urged you to check if there were any new releases. At the time, given the nature of cryptocurrency mining, we were using MinIO extensively.

My advice would be to go through the manual slowly to understand every aspect of MinIO. That helps you grasp how it works and how it needs to be installed and what the requirements are. They have very good representation.

My primary use case for MinIO is as a tool for document management and storage.

The benefit of MinIO is that it's more secure. It also facilitates our works due to the facility of its end-point course.

MinIO's most valuable feature is that we can send a lot of detail in the bottom of the core of the end-point, in a way that is easy and interactive. It also saves a lot of time in generating and managing documents.

An area that could be improved is the limited storage provided in the free version of this tool. When handling a lot of documents, the interaction can take a lot of time.

I've been using MinIO for the last two to three years.

The stability of this solution is fine, though sometimes the duration of responses is too long.

MinIO is easy to scale.

The initial setup was not easy at all. We had some problems since we weren't given the information on how many instances needed to be deployed the first time, which blocked our deployment. It took us one or two days to deploy the product. On the other hand, it was very easy to manipulate and interact with.

I think MinIO is the most efficient tool in the management of documents, and its performance facilitates our works. I would rate this tool as seven out of ten.

My primary use case is to help our customers integrate with MinIO to do file-sharing collaborations.

MinIO made it easy to collaborate with Amazon SDK.

The most valuable feature is file storage.

The product's security is open by default, without any SSL, which could be an area for improvement. I don't think I would request any new features in the next release, as the product currently meets all my needs.

I have been using MinIO for about six months.

The stability of this solution is great - with any file that we uploaded or downloaded, we found it was quick to respond.

My impression is that MinIO supports a wide range of clustering, and I believe it should work in a highly scalable environment for people with larger platforms and larger storage.

The initial setup was very easy - one click, and it was installed. That's what is great about MinIO.

MinIO is open source, but it also has an enterprise license available if preferred.

I feel MinIO is the best solution to recommend to anyone who requires on-premise S3-compatible storage. It is easy to install, easy to configure, and you can get it up and running in minutes, not hours or days. I would rate this product as nine out of ten.

We are a solution provider and I am working on a project that is using MinIO for storage.

The most valuable feature is the ease of management and administration. I do not have a system administrator in my project, so the simplicity of management is important to me.

The monitoring capability is really bad and needs to be improved. There are no monitoring tools available and there are several metrics that I would like to keep track of. Without good usage monitoring, it will be very hard to use in production.

In my opinion, the monitoring feature should be added to minIO in order to give administrators efficient data including bucket information(size, load on it, requests …), the CPU usage, running/ stuck/blocked threads, queue of thread pools, free/max heap percent, request per object in buckets and ...

I think providing REST API for monitoring and configuration makes it easier to use.

If I can set up MinIO to run as a service then it will be more stable.

Enhancing the user interface with more options would be a nice improvement.

I have been using MinIO for two years.

It is a stable product and I use it every day. If I were able to set it up as a service then the stability would be improved.

MinIO is scalable, although we do not rely on that right now. In the future, we will be expanding it. At this time, we have a team of five developers who are using MinIO.

I have not needed support to this point, as I seek help in the community when I have issues. Furthermore, because we are located in Iran and under sanctions, were are not able to purchase technical support.

I used to use Red Hat Ceph Storage, but it is more complex than MinIO and very difficult to manage because I do not have a system administrator on my team.

The initial setup is very simple. It took me about 15 minutes to deploy five instances that had Java on it.

I can easily deploy this solution using the command prompt.

This is an open-source solution but I am using the licensed version.

When I began this project, I researched several options for storage that were alternatives to Red Hat Ceph. I found that MinIO is the best choice for this project because of the API support.

My advice for anybody who is implementing MinIO is to visit the website and view the documentation. It is very complete and is helpful. 

This is a good product choice for startups that don't have a system administrator. It has a good API and it's easy to use. My main complaint is about the lack of monitoring tools.

I would rate this solution a nine out of ten.