|
| 1 | +# What is Oxia? |
1 | 2 |
|
| 3 | +--- |
2 | 4 |
|
3 | | -# What is Oxia |
4 | 5 |
|
| 6 | +<div style={{display: "flex", justifyContent :"center", flexDirection: "column", alignItems : 'center'}}> |
| 7 | + <img style={{width: '80%'}} src={"/banner.svg"} alt={"Banner"}/> |
| 8 | + <span style={{fontSize: '0.7rem', marginTop: '0.2rem'}}>Original image credited to xkcd.com/2347, alterations by Qiang Zhao.</span> |
| 9 | +</div> |
| 10 | + |
| 11 | +Oxia is positioned as a modern, horizontally scalable metadata store and coordination system designed to address the |
| 12 | +limitations inherent in traditional systems within large-scale distributed environments. |
| 13 | + |
| 14 | +It is engineered to serve as a core infrastructure component, particularly for high-performance data streaming platforms. |
| 15 | + |
| 16 | + |
| 17 | + |
| 18 | +## Why Oxia? |
| 19 | + |
| 20 | +Oxia directly confronts the central challenge of balancing scalability, latency, and cost efficiency within contemporary |
| 21 | +data streaming infrastructures. Many organizations frequently encounter a dilemma, compelled to choose between scaling |
| 22 | +their data operations to meet demand and maintaining manageable costs. |
| 23 | + |
| 24 | +Oxia is specifically designed to alleviate issues observed in existing coordination systems such as Apache ZooKeeper, Etcd, and Consul. |
| 25 | + |
| 26 | +It achieves this through a set of key features, including: |
| 27 | + |
| 28 | +- [Sharding Based Architecture](https://en.wikipedia.org/wiki/Shard_(database_architecture)) |
| 29 | +- [Standard Key-Value API](https://en.wikipedia.org/wiki/Key%E2%80%93value_database) |
| 30 | +- Full Features as Metadata Store |
| 31 | +- High W/R Performance Based on the [LSM-Tree](https://en.wikipedia.org/wiki/Log-structured_merge-tree) |
| 32 | +- Policy-Based Shard Placement |
| 33 | +- Automatic Operation and Disaster Recovery |
| 34 | +- Modern Observability based on the [Open-Telemetry](https://opentelemetry.io/) |
| 35 | + |
| 36 | + |
| 37 | +## Who is using Oxia? |
| 38 | + |
| 39 | +Oxia is suitable for a wide variety of use cases, including: |
| 40 | + |
| 41 | +<br/> |
| 42 | +<br/> |
| 43 | + |
| 44 | +import { Table } from 'nextra/components' |
| 45 | + |
| 46 | +<Table> |
| 47 | + <thead> |
| 48 | + <Table.Tr> |
| 49 | + <Table.Th>Project Name</Table.Th> |
| 50 | + <Table.Th>Usage</Table.Th> |
| 51 | + </Table.Tr> |
| 52 | + </thead> |
| 53 | + <tbody> |
| 54 | + <Table.Tr> |
| 55 | + <Table.Td><a href={"https://pulsar.apache.org/"}>Apache Pulsar</a></Table.Td> |
| 56 | + <Table.Td>metadata storage for supporting more than one million topics</Table.Td> |
| 57 | + </Table.Tr> |
| 58 | + <Table.Tr> |
| 59 | + <Table.Td><a href={"https://bookkeeper.apache.org/docs/overview/"}>Apache Bookkeeper</a></Table.Td> |
| 60 | + <Table.Td>metadata storage</Table.Td> |
| 61 | + </Table.Tr> |
| 62 | + <Table.Tr> |
| 63 | + <Table.Td><a href={"https://streamnative.io/products/ursa"}>StreamNative Ursa</a></Table.Td> |
| 64 | + <Table.Td>metadata storage and index storage</Table.Td> |
| 65 | + </Table.Tr> |
| 66 | + </tbody> |
| 67 | +</Table> |
0 commit comments