forked from openebs/openebs
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
23 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,23 @@ | ||
### Company: Optoro (https://www.optoro.com/) | ||
|
||
### Stateful Applications that you are running on OpenEBS | ||
- Postgres | ||
- MySQL | ||
- Kafka | ||
- Redis | ||
- ElasticSearch | ||
- Prometheus | ||
- Thanos | ||
|
||
|
||
### Type of OpenEBS Storage Engines behind the above application - cStor, Jiva or Local PV? | ||
100% zfs-localpv | ||
|
||
### Are you evaluating or already using in development, CI/CD, production | ||
OpenEBS is the default in all of our baremetal kubernetes environments. | ||
|
||
### Are you using for home use or for your organization | ||
We use OpenEBS to power Optoro's Optiturn Platform. | ||
|
||
### A brief description of the use case or details on how OpenEBS is helping your projects. | ||
The vast majority of applications are able to better handle failover and replication than a block level device. Instead of introducing another distributed system into an already complex environment, OpenEBS's localPVs allow us to leverage fast local storage. Additionly, by leveraging ZFS we are able to have encryption at rest for all of our workloads, compression, and the piece of mind of a COW based filesystem. OpenEBS has allowed us to not introduce a complicated distributed system into our platform. The adoption has been smooth and completely transparent to our end users. |