Project: Backend Operators Redesign
@ethany-nv is already working on this.
Since Dec 12, 2025.
- Dominant language
- Python
- Stars
- 260
- Forks
- 57
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 69
Description
Have you read the Project Process docs?
- Yes, I have read and understood the RFC docs
Summary
This project aims to redesign the OSMO backend operator component to address critical scaling, reliability, and performance issues.
Person in Charge (PIC)
@xutongNV
Motivation
To prepare for future growth, OSMO's backend operators require architectural enhancements to support production workloads for Kubernetes backends at large scale. The current system provides a solid foundation, but can be optimized in several key areas: system stability under sustained load, event delivery consistency, and workflow status update latency.
This redesign will proactively strengthen OSMO's ability to support production-scale deployments reliably and efficiently as customer workloads continue to grow. Rewriting the backend listener using Golang will allow us to leverage native Kubernetes Go library for more performant operations and more built-in features (such as node/pod events caching).
Problem
- Scaling - Single-threaded listener design limits workflow throughput
- Reliability - Frequently restarts, and event drops
- Performance - Memory leaks consume several GB per instance, and workflow status updates experience high latency
References
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.