MinIO Reviews

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 use the solution for object storage in our core platform. It works best as a data lake solution for us.

The solution is simple to use and maintain for DevOps executives. Also, it has the best performance compared to other solutions.

The solution's features for distributed non-container applications and reverse proxy could be better.

I have been using the solution for three months.

It is a stable solution. I rate its stability ten out of ten.

It is a scalable solution. It uses consistent patching; thus, it is more scalable than other solutions. Although, we encountered a few scalability-related issues while introducing a new node.

We used Azure solution before. It was challenging to maintain the Kubernetes cluster.

The solution's initial setup was straightforward. We deployed it through Ansible playboards. It took about three days to complete.

We use the solution's open-source version.

I recommend the solution to start-up businesses. It is the best tool in the market if they want a simple and low-maintenance product. Also, it requires DevOps expertise for the smooth functioning of scalability and reverse proxy features.

I rate it eight out of ten.

We use MinIO for enterprise file storage.

I have been using MinIO for approximately three years.

The stability of MinIO is good.

The scalability is one of the limitations we have found. We are looking for another solution but they must provide the same characteristics, such as an affordable price and continuity.

We have approximately 100 of my colleagues that are using the file service.

I have not needed to use the support.

The initial implementation was straightforward. It took us three days for the process.

We use our in-house team of two to do the implementation. The maintenance is done by three people 10 days out of the year.

MinIO is a free open-source solution.

I rate MinIO an eight out of ten.

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.

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 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 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.

Generally speaking, we use MiniIO for storing unstructured or semi-structured data. In my current project, we were using it for the semi-structured data. We also use MinIO as a data link. The data is transformed and loaded onto MinIO. And MinIO is used to rate the statistics based on the data.

So I'll just briefly explain how the entire flow works and how the data comes into the menu. After we transform the data, we input it into MinIO. The raw data is in different formats. It is in a delimited, positional-specific, or some other format. And three types of data—virtual, date and time, and numeric—are being loaded, including all Python and Java date formats and various kinds of normal data. Once we transform the data, we load it onto MinIO.

The development and QA teams are the primary users. They work on MinIO together to load the data. So, for the lower environment, the subsequent systems directly read the data from the menu and then utilize it for visualization. The actual end-customer is not reading the data directly from MinIO.

Earlier, the organization experienced some issues transforming the data and loading it into the technology, so we adopted Spark, and the data was to be loaded onto the menu, MinIO. In terms of the volume, processing speed, and accessibility of data, MinIO was outstanding. First, it worked well for storing large volumes and sizes of data. Second, you can retrieve, load, or transform data with MinIO quite fast. It is a backbone to the organization because it loads the data and stores it after transformation, then all the lower systems can use it.

For starters, MinIO has a good user interface. You can access it through the browser and perform operations like creating the object. And inside that, you can make the bucket manually. You can also access it through the command-line interface. Using the command interface, you can perform a complete set of operations — create the bucket, open it, read the data, delete those buckets, etc. — and it is pretty fast 

The Distributed User Interface (DUI) needs some work. It's hard to view a large set of data on the DUI. It's an issue with the DUI's performance. One way to improve this would be to allow a large set of data to be directly viewed on the UI. Usually, business people do not access the data through the command-line interface. So the DUI tool could be helpful if MinIO improves its performance and ability to handle a larger sample of data. When you're working with a small set of data, the DUI can download that quite easily. But if the data set is vast, it takes time. It becomes quite challenging to view that or download that data. So maybe introducing a PLI command-line interface could improve the DUI function. That would be very useful for the end-user.

I've been working with MinIO for about a year and a half to two years.

We have not faced any stability issues or had any problems accessing the data on MinIO that I can recall.

I think scalability-wise, MinIO is quite good. However, we had to do some MinIO cleanup activity on the lower environments. By lower environment, I mean the test or development environments. So we had limited capacity in the lower environments. But overall, we have not faced many issues in terms of scalability. Space was available whenever it was required. On the other hand, we could not automate scalability. We had to perform cleanup activity on the lower environments manually.

I haven't interacted with the MinIO technical support.

I did not help set up MinIO, so I will not be able to answer that question. An in-house DevOps team deployed it. Installing new versions of MinIO does not take much time. The entire deployment process took around two days for us, including deploying the code of different modules or different features. But I don't think the basic setup of MinIO took a very long time. It was installed in 10 minutes or so. The DevOps team, which includes around three to four people, upgrades MinIO from time to time.

I rate MinIO eight out of 10. It has a good UI, and it allows you to use the command line, which has a solid list of operations that you can perform. My advice to anyone who implementing MinIO is to take advantage of the command-line interface. It's pretty good to use. If you use the command line wisely, it is a highly efficient feature.