-
Notifications
You must be signed in to change notification settings - Fork 383
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
Add User Story #1882
Add User Story #1882
Conversation
Oh, thanks for taking the time to write that. I will have a look soon. |
It also provides profiles, which allows us to have slightly different configurations or behaviors between environments. | ||
We can easily substitute some hard-to-run third-party services with local mocks, leaving the application code unchanged. | ||
Quarkus is also great in terms of configuration and how easily we can overwrite values stored in the application.yaml file with external environment variables. | ||
Although the hot reload mode didn't work well with Kotlin, I believe all the bugs related to it will be solved in upcoming releases. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
got links to some of those bugs you encountered?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can easily substitute some hard-to-run third-party services with local mocks, leaving the application code unchanged. | ||
Quarkus is also great in terms of configuration and how easily we can overwrite values stored in the application.yaml file with external environment variables. | ||
Although the hot reload mode didn't work well with Kotlin, I believe all the bugs related to it will be solved in upcoming releases. | ||
During development, we had to restart our running service most of the time for code changes to take effect. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
which version of Quarkus were you targetging?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
3.6.1
During development, we had to restart our running service most of the time for code changes to take effect. | ||
|
||
Our backend API functionalities took approximately a month and a half to complete. | ||
Considering that only two developers worked on the backend, I think it was an okay result. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
okey? is that a bad okey or a good okay ? :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@maxandersen I updated the wording slightly. Yes, the result was good, indeed
Whoops. Missed.this in the queue. Mentioning myself @maxandersen and @gsmet to see it when back Monday. |
I said LGTM. I made a few very minor changes (mostly change the publication date, uncapitalize the titles and make sure dashing of various keywords was consistent across the post). I wasn't able to push to your branch so I created another PR to get it merged: #1953 . I squashed your commits and made my adjustments in a separate commit if you wanted to have a look. I'm closing this one in favor of the other one :). |
** If you are updating a guide, please submit your pull request to the main repository: https://github.com/quarkusio/quarkus/tree/main/docs/src/main/asciidoc **