Amazon Elastic Block Store (EBS) from AWS is designed for application workloads that benefit from fine tuning for performance, cost and capacity. Typical use cases include Big Data analytics engines (like the Hadoop/HDFS ecosystem and Amazon EMR clusters), relational and NoSQL databases (like Microsoft SQL Server and MySQL or Cassandra and MongoDB), stream and log processing applications (like Kafka and Splunk), and data warehousing applications (like Vertica and Teradata).
N/A
Google Cloud Storage
Score 8.4 out of 10
N/A
Google Cloud Storage is unified object storage for developers and enterprises.
Basically, we choose EBS because we are using AWS, we have already evaluated 3 cloud providers AWS, GCP, and azure. And we decided to use AWS because of some elements. Mostly because AWS has a native Linux operating system (amazon Linux).
Amazon Elastic Block Store is a very good scaling solution for storage if you are invested in AWS. It provides a quick and easy way for you to easily get all the storage you need at and adjust it if you need more or less storage for your projects.
It provides the optimized storage performance and cost for your workload and these options really work with SSD-backed storage and it improves the database performance. Keeping backups of your EC2 resources, including EBS volumes is a little bit tricky and its takes some more time and increase through put is also a tiring job to do.
[Google Cloud Storage is] great for storing and playing large video files, and even sharing them securely with others, whether or not they are part of your organization. No need to download video files before watching, and can also be used to store any other kinds of files.
Perhaps the strongest advantage of Google Cloud Storage is that they seem to update files quicker than competing cloud storage providers. The software rarely runs into sharing violations or access issues.
Google Cloud Storage has a unified API, which is nice when authorizing others to access data.
The software rarely fails and handles large volumes of data well.
after all of the investment made in the tool and considering how many teams use it I think we would not be likely to move away from this tool. A lot of our information including historical is already here and we are happy with the capabilities of the tool currently
Amazon EBS is a great tool and fairly easy to use as long as you are familiar with the Amazon Web Service ecosystem. It allows a great way for you to move storage around easily and allows you to quickly provision storage as needed based on the business requirement. For us, it's easy to move between our EC2 images that had been linked with EBS storage between these Amazon accounts.
Very easy to use. I love having my data backed up. I love that Google Cloud Storage provides me with the peace of mind that I no longer need to worry about my data being lost. I can now sleep better at night. Google Cloud Storage is very easy to use. Overall, you save time and have less stress by using Google Cloud Storage.
Excellent upload and download performance, excellent UI and a robust set of tools make GCS a must-have tool in our overall technical stack. Since we use so many data processes, GCS is a clutch player to help us orchestrate both input, intermediate storage, and output of all of these data processes. Because it's one tool for all of these processes, our applications get the benefit of having to need only one SDK to work against.
The support for Amazon Elastic Block Store is great as long as you can articulate your needs. Like most tools, there may be some back and forth before you find a support person that is knowledgable in the tool and can provide you with necessary insights.
We have never used official support from Google for our Google Cloud Storage, but there is plenty of documentation in place already. With a small amount of work, anybody should be able to get started. Once needs get more complicated, there is still documentation from Google, but also plenty of community support for common use cases around the internet.
overall I was not directly involved but hears the teams were satisfied with the implementation. the teams that used the tool did not encounter major issues, it was as expected with minor issues and bugs that were resolved later. The more significant learning curve was actually starting to use the tool
So far I have only used Amazon Elastic Block Store (EBS) and Azure but comparatively [I] prefer AWS elastic Block store as its having more advantages than Azure and I found it quite satisfactory and it helped a lot for information storage. We are not looking for any other hosting provider at this time.
We prefer Google Cloud Storage over Amazon Web Services because of the tools and code integration offered by Google Cloud Storage. We found the Google Cloud Storage toolset to be highly usable and give us the fine-grained control we need for managing digital assets. Ultimately, we chose Google Cloud Storage because we found the API and suitability for code integration with our Java codebase to be impeccable and because we had excellent direct support from the Google Cloud Storage team
When your application needs high IOPS storage, this is a great solution that will keep your business functioning.
Without Amazon Elastic Block Store you could try spreading your data across several standard drives, but that introduces complexity and still has IOPS limits.
It has assisted greatly with our ability to share documents/information cross functionally. Especially within our advertising team, we store a large amount of information to assist new hires and refresh current employees.
Something that could improve is employees' understanding of how to best utilize Google Cloud Storage. This could improve by implementing a potential training video or tutorial.
Overall, Google Storage has been great. I have not used a similar storage product that had the same enterprise level capabilities.
