Overall Satisfaction with Amazon Elastic Block Store (EBS)
We are integrating an open source web3 protocol called matrix.org to build our internal communication and chat platform. We are enabling Slack, Whatsapp, Discord, Instagram for our internal and external use. When using all these channels media and content gets shared between our various users and the current version of matrix does not provide a direct way for us to store the content on S3. Hence we added a EBS Volume on a general management server and then using NFS we attached it to our matrix servers. This way when we autoscale our matrix servers, the NFS bonds between the EBS and matrix servers allows us to share the stored content instantly with the newly spawned matrix servers.
- High Performance & Instantly Available on Demand
- Differential Prizing as per requirement
- Long term durability
- Network Latency can be an issue sometimes
- It can become tedious to figure out the linkage between EBS & the volume mounted on the servers, especially if one is using multiple EBS
- Naming conventions can be confusing, it's not automatic and if user is dis-organised then it can lead to confusing
- Easy Management
- Availability, Durability & Longetivity
- Cost Effective
- Its a good tool to have in your software arsenal
- Very effective as it has allowed us to move/provide data between servers seamlessly
- reduced downtime and improved devops management processes
Its comparable, but overall I think the user interface to manage Disk Block Storage is better in AWS compared to Google Cloud
Do you think Amazon Elastic Block Store (EBS) delivers good value for the price?
Yes
Are you happy with Amazon Elastic Block Store (EBS)'s feature set?
Yes
Did Amazon Elastic Block Store (EBS) live up to sales and marketing promises?
Yes
Did implementation of Amazon Elastic Block Store (EBS) go as expected?
Yes
Would you buy Amazon Elastic Block Store (EBS) again?
Yes