Amazon Elastic Block Store (EBS) Review
Rating: 10 out of 10
IncentivizedUse Cases and Deployment Scope
We are serviecing out customers implementation of in-house projects and SaaS product businesses for B2C markets. We are mostly dealing with object storages, especially for meta data dependent projects but for the large corporate use we experienced Amazon Elastic Block Store (EBS), which is targeted for Mission critical infrastructure. The scope was large corporate reporting systems, based on implemented ERP (SAP AG) to have precise and frequently updated reporting server and dependent on frequent update industrial infrastructure which needed low latency connectivity of devices.
Pros
- Raw storage capacity attached to your instance operative system
- Frequent data rewriting (mission critical for reporting)
- Low latency connectivity (14 reporting subsidiaries in different time zones)
- Videly spreaded for implementation
- Fast accessible drive
- Block storage are core for Java, Net mobile applications
Cons
- Amazon Elastic Block Store (EBS)does not fit for in-depth analytical systems having no internal data schema (metadata) applicable - so you need one more data base to map
- Pricing should be according to the space used for large institutional users (% of capacity)
- Fragmented data some times requers more sophisticated access versus API
- Binded server for system runing (no external access), critical for DevOps
Likelihood to Recommend
If you need to run ultimate, high scale application for frequently updated data with permanent recovery point update - use block storage especially if you are core Java, MSFT Net developer. It has faster input/output capabilities and rapid access, but limited only for current instance nor any external server call. It will not fit your demand for building in depth analytical system, cause missing build in data schema, and using separate data base for mapping metadata could slow and limit access. Since of 2000-th Elastic is more then classics, so is a choise of your architectore if it suit your business objective. There is no field for failure, so choose type block or object before you have started implementation. Works good for data warehousing of missiong critical parts of ERP and decision making apps.