Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Announcing Kubero v3 (Refactoring) #623

Open
mms-gianni opened this issue Feb 3, 2025 · 3 comments · May be fixed by #619
Open

Announcing Kubero v3 (Refactoring) #623

mms-gianni opened this issue Feb 3, 2025 · 3 comments · May be fixed by #619
Assignees

Comments

@mms-gianni
Copy link
Member

mms-gianni commented Feb 3, 2025

Hey everyone

We’re excited to announce Kubero v3, a major update that brings significant improvements and introduces a major architectural change: Kubero will be built on NestJS!

Why

Kubero was initially built as a Proof of Concept during Heroku's major outage in 2022. Although there was an improvement in v2 are some parts of the code still the same. And let's be honest: They are not best practice of coding.

Why NestJS?

NestJS is a progressive Node.js framework designed for scalability and maintainability. By leveraging modern development patterns, NestJS helps us bring a more robust, testable, and developer-friendly experience to Kubero. It should be compatible, since it uses Express and PassportJS

Key Benefits of Moving to NestJS

  • Modular Architecture: The NestJS framework allows us to better organize and scale Kubero’s features while maintaining cleaner codebases.
  • Enhanced Performance**: With built-in support for asynchronous operations and optimized routing, Kubero is now faster and more responsive.
  • Improved Developer Experience: NestJS provides a structured, opinionated approach that simplifies development, testing, and maintenance.
  • Scalability: Designed with enterprise-grade applications in mind, NestJS enables us to future-proof Kubero for even larger and more complex deployments.
  • Extensive Ecosystem: The NestJS ecosystem, with its integration libraries and support, helps us provide powerful new features faster and more efficiently.

All features should be migrated. Even the API should have a backward compatibility.

You can follow the progress in this branch here:
https://github.com/kubero-dev/kubero/pull/619/files

@mms-gianni mms-gianni self-assigned this Feb 3, 2025
@mms-gianni mms-gianni pinned this issue Feb 3, 2025
@mms-gianni mms-gianni linked a pull request Feb 3, 2025 that will close this issue
12 tasks
@mms-gianni
Copy link
Member Author

mms-gianni commented Feb 10, 2025

Making some progress here ... still a lot of work to do.

Image

Some routes will change
Image

@jfmatth
Copy link

jfmatth commented Feb 12, 2025

Love to see the improvements. I'll have to give v3.0 alpha+ a try 😄

@mms-gianni
Copy link
Member Author

Great to hear you @jfmatth . I'll let you know 😉

Hit the 20K mark. And still a lot to do.
Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants