Amazon Elastic Block Store (EBS) vs. Longhorn Block Storage

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.

Incentivized

Longhorn Block Storage is well suited for most Kubernetes workloads where data storage is required, but when very high storage speed is essential, Longhorn Block Storage might not be the best solution. For those rare situations, we use local storage mounts. Longhorn Block Storage's ability to easily create/restore volume snapshots is a very frequently used feature among our dev teams because they can easily play multiple scenarios with the same data - modify data, restore it and modify it again.

• 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

Incentivized

• Creates read-write many (RWX) volumes
• Longhorn Block Storage is an easy to deploy solution
• Scheduled and on-demand volume snapshots can be created using web GUI
• Volume backups can be stored offsite on any S3 compatible storage solution
• Backups and snapshots can be restored using web GUI

• Creating too much EBS can be disaster if you are not properly organized by tags
• In terms of pricing it's a bit on higher side.
• In terms of performance, there is room for improvement as sometimes reading or saving the data can be painful.

Incentivized

• Version to version upgrades takes more expertise to do than initial deployment
• If something goes wrong, you will need a help from support
• Longhorn Block Storage speed is slightly slower than local disk storage speed

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.

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.

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.

Incentivized

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

Incentivized

• It has provided a highly available storage solution for almost all our Kubernetes deployments
• We can deploy new app versions with peace in mind because we have working data backups
• Application development is faster because devs can play with data and easily restore it when needed