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

Move to Quarkus #581

Open
FabriDamazio opened this issue May 28, 2022 · 4 comments
Open

Move to Quarkus #581

FabriDamazio opened this issue May 28, 2022 · 4 comments

Comments

@FabriDamazio
Copy link

The main advantage of developing Java applications with Quarkus is a gain in performance. This is particularly important when using Java applications in container environments. Performance benefits include:

  • Fast application start-up time
  • Low memory consumption
  • Almost immediate scaling of services
  • Lower space requirements for native images

In addition to the performance advantages, Quarkus shines because of its user-friendliness. Experienced Java EE and Spring developers can easily learn to use the framework. They also benefit from the fact that Quarkus is based on a solid framework. The following standard technologies are used, in addition to others:

  • Eclipse MicroProfile
  • Spring Dependency Injection
  • Hibernate ORM

Quarkus also offers a live coding environment, in which developers can quickly prototype. The live reload feature contributes to smooth development.

IMPORTANT UPDATE: In our last sync meeting with the Information Security committee and the Risk committee, we presented our proposal to migrate to Quarkus and it was rejected.

Only a proof of concept was approved. The budget for hiring 4 squads (1 product owner, 1 scrum master, 4 back-end developers and 2 QAs each) will be voted on at the next meeting with the Finance Department and, if we have the approval of our CFO, the strategic initiative will be included in the OKR .

@GEOEGII555
Copy link

GEOEGII555 commented Nov 2, 2024

See #694 - C++ is a lot faster in terms of performance.

@FabriDamazio
Copy link
Author

See #694 - C++ is a lot faster in terms of performance.

C++ is not an approved language by the team responsible for evaluating tools and technologies for use within our organization. The rationale provided is that C++ increases complexity and associated costs in recruiting and onboarding development talent.

@GEOEGII555
Copy link

See #694 - C++ is a lot faster in terms of performance.

C++ is not an approved language by the team responsible for evaluating tools and technologies for use within our organization. The rationale provided is that C++ increases complexity and associated costs in recruiting and onboarding development talent.

Are you sure? I asked that team and they approved it: #693 (comment)

@FabriDamazio
Copy link
Author

See #694 - C++ is a lot faster in terms of performance.

C++ is not an approved language by the team responsible for evaluating tools and technologies for use within our organization. The rationale provided is that C++ increases complexity and associated costs in recruiting and onboarding development talent.

Are you sure? I asked that team and they approved it: #693 (comment)

After discussions with my leadership, this matter has now been escalated to the board of directors. It’s scheduled for review in the quarterly alignment meeting, meaning this change will remain on hold for the time being.

Please ensure that everyone involved is copied on these communications—including myself, my manager, my manager’s leader, and the supervisor—so that all parties are aligned.

As we’re currently observing a freeze period due to Black Friday and the holiday season, any action on this change will naturally have to wait until next year. Assuming budget and priority allow, there might be room to consider this improvement for Q4 in next year’s roadmap.

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

No branches or pull requests

2 participants