Prioxity - High-Performance Distributed message and WASM bytecode queue

Designed for baremetal Linux-based servers
Built for distributed WASM code execution
Promoted WASM bytecode for distributed libraries that update in real-time

About Prioxity

Prioxity's release date is TBD.

Prioxity is a high-performance distributed message and WASM bytecode queue designed for baremetal Linux-based servers. It supports messages, ephemeral WASM bytecode, and promoted WASM bytecode that can be used a distributed shared library that updates in real-time with hash-based versioning.

Prioxity is built with Odin and uses lock-free SPSC queues for maximum performance. It also leverages DPDK for high-performance network operations.

Prioxity will be open-source on release.

Use Cases

Prioxity is designed for baremetal Linux-based servers. It can run on cloud-based servers or Kubernetes clusters, but there is more effort required in setting up a proper environment. Additionally, Prioxity tries to rely heavily on NUMA-aware threads for performance. Designing a proper environment for Prioxity therefore requires configurations that are designed for CPU pinning. AWS offers metal instances and on Kubernetes you can do this with Topology Manager and 'single-numa-node' settings. For maximum performance, additional configuration parameters are recommended such as disabling SMT on Linux.

Some use cases for Prioxity include:

Any use case that requires high-performance and distributed computing can be supported by Prioxity. Each task can take advantage of pinned WASM bytecode / functions as a shared library, or producers can send ephemeral WASM bytecode to be executed by workers. Messages can include the hash of a pinned WASM function that can accept the message as an argument, and a worker that picks up the message will execute it with the pinned WASM bytecode.

Contact

Drop me an email at gerardo @ gerardo.com if you're interested or want to work on Prioxity!