Google Cloud Storage Reviews

I am working with Supabase and Chroma for storing, and I also use Supabase Vector with its features for storing embeddings.

With it, we started with Supabase, and we use it for storing a regular database and as Supabase Vector to store our vector embeddings from retrieval generation.

I usually work with databases using Supabase and MongoDB, but I don't usually work with these because my main work is in medical segmentation.

I'm currently using Google Cloud Storage. I'm using Google Cloud for several services including Google Cloud Run, where I deploy some web apps. I also buy virtual machine instances from Google Cloud and use their storage; everything is on Google Cloud.

I use Google Cloud Storage because it's not expensive to use, and I usually store some medical data on it. It's easy to integrate with the virtual machines provided by Google, so I can connect to it directly and access the files.

The most useful aspect of Google Cloud Storage is that I can connect it with my virtual machine easily.

The firewall options provide really good security while working on the storage.

To simplify everything in Google Cloud Storage, having a function that automatically compresses files would be great. I'm not sure if it's a feature that exists because I've been working only for four or three months, but for compressing files, perhaps if some files are uploaded and not used for a long time, they could be automatically compressed.

I just keep some of the documents in the solution. I think I just keep some specific documents that I cannot keep on my laptop. I just put them on Google Drive.

The most valuable feature of the solution is reliability. It replicates our exploring window. Whatever we can do on our hard drive, in the C drive or D drive, we can do it in the cloud. We can carry the data in the tool anytime without even carrying our laptop. Specific features in the tool are some enhancements, like uploading files. One good feature of the tool is that we can just drag and drop all the folders, and it gets updated.

Our primary use case for Google Cloud Storage is for backup storage in the cloud, just in case our on-premises server fails. We do not use it as a primary storage solution but for backup purposes.

We have found our user experience to be excellent when it comes to storage. Google Cloud Storage meets our needs and requirements, without any disruptions.

I use Google Cloud Storage to store data files, images, and videos collected from operations. All documents and attachments are uploaded via API to the cloud. We are migrating from physical files to digital documents stored in Google Cloud Storage. Additionally, I use it for a Bible app to store Bible data files in the cloud.

Google Cloud Storage has enabled us to migrate from physical files to digital documents, significantly enhancing our document management workflow. It allows the department to store and manage data efficiently.

I use Google Cloud Storage to store my emails and attachments from Gmail. I also use it to store my Android phone's videos, photos, and some additional documents. 

I find the accessibility from various devices to be the most valuable feature of Google Cloud Storage. I also like that it is integrated with Gmail and Google Groups.

Drive pulls in the structure from my computer and recent documents. Nothing very expensive.

You can perform your data queries the same way using BigQuery. That's one of the advantages. You don't need to learn anything new. Whatever SQL queries you know, you can implement there.

Any developer can study and implement what we do for cloud operations with the database side. It's not a big deal for developers. They can implement things using Google Cloud Storage.

Google Cloud Storage provides good safety measures. They use tokens for access control, which means nobody can access the data without proper authorization.

If you compare it with other cloud services like Azure, there might be some glitches in Azure. However, from my experience, Google Cloud Storage is very stable.

From a security perspective, I've never tried to hack it myself. There might be potential for brute force attacks to get into the application, but that's just speculation. It would be quite difficult to breach from a developer or normal user perspective.

The main area for improvement would be providing a local setup or working area. Currently, developers need to commit code to test changes. A lower-cost option for this would be beneficial.

A system similar to Bitbucket would be advantageous. At present, data personnel complete their work, commit the code, and then deploy it to the Kubernetes engine. A Bitbucket-like system would simplify this process for developers.

The solution's most valuable features are availability, feasibility, and reachability. Google Cloud Storage is the best solution because it is easy to handle. New users can easily grab this technology and start using it because it's a user-friendly product.

I have been using the solution for the last two years. My storage team is working with Google Storage. My storage team has connections to the ISPs, and they are migrating their data from one location to another with the help of 3PAR.