Migration of Onyxia API to Go #925
trygu
started this conversation in
Show and tell
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
We are excited to announce the planned migration of the Onyxia API to Go! 🚀
Why this Migration?
The Onyxia API is a core component of the Onyxia service, responsible for handling Kubernetes environments, including namespace management, access control, and service configuration. The existing Java-based API has presented challenges in security, maintainability, and performance. Migrating to Go will bring:
✅ Enhanced Security - Addressing past vulnerabilities and ensuring compliance with best practices.
✅ Better Maintainability - A cleaner, more modular codebase that is easier to extend.
✅ Multi-Region Support - A future goal is enabling Onyxia API deployments in multiple regions.
✅ Improved Performance - Go's lightweight concurrency model is better suited for high-parallelism workloads.
The Migration Plan
The transition will happen in three phases:
Phase 1: Foundation & Tracer Bullet API (Q1-Q2 2025)
onboarding
andbootstrap
services.onboarding
service will handle Kubernetes namespace creation.bootstrap
service will manage Onyxia Web configuration and multi-region metadata.Phase 2: Core API Migration (Q2-Q3 2025)
Phase 3: Full Transition & Java API Deprecation (Q3 2025)
Follow the Migration!
This project is open-source and welcomes contributions and feedback. Development is happening in our new GitHub repository:
➡️ Onyxia Onboarding Repository
We will share updates as development progresses. Feel free to engage, ask questions, or contribute! 🚀
Beta Was this translation helpful? Give feedback.
All reactions