add blog about reactive renaming #1913
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
😭 Deploy PR Preview failed. |
cescoffier
previously requested changes
Mar 13, 2024
| - *Quarkus SmallRye Reactive Messaging* is now *Quarkus Messaging*, indicating its broader use cases. | ||
| - Extensions that inherently push for a reactive programming model, like *Quarkus Hibernate Reactive*, will retain the "reactive" terminology. | ||
| - The *Quarkus REST Client Reactive* is simplified to *Quarkus REST Client*, unifying the naming under a more general "REST" umbrella. | ||
|
|
There was a problem hiding this comment.
Quarkus REST, Quarkus Messaging and Quarkus REST Client are still leveraging the reactive engine underneath for efficiency and performances. At the user level, this is an implementation details.
geoand
reviewed
Mar 14, 2024
|
|
||
| Historically Quarkus has used the term "reactive" in the names of several extensions to indicate their *additional* support for non-blocking, event-driven programming. | ||
|
|
||
| However, we've found that this terminology has led to confusion and misunderstanding among our users. Many have mistakenly believed that using these "reactive" extensions forces them into reactive programming, even though Quarkus always by default recommend traditional blocking programming model for your application and only optionally use reactive. |
There was a problem hiding this comment.
Suggested change
| However, we've found that this terminology has led to confusion and misunderstanding among our users. Many have mistakenly believed that using these "reactive" extensions forces them into reactive programming, even though Quarkus always by default recommend traditional blocking programming model for your application and only optionally use reactive. | |
| However, we've found that this terminology has led to lots of confusion and misunderstanding among our users. Many users mistakenly believe that using these "reactive" extensions forces them into reactive programming, even though Quarkus always by default recommend traditional blocking programming model for your application and only optionally use the reactive programming model. |
|
|
||
| == Impact on users | ||
|
|
||
| These changes are designed to make it clearer that you're not constrained to reactive programming when using these extensions. Whether you prefer a traditional blocking approach, reactive programming and/or virtual threads, Quarkus supports you. |
There was a problem hiding this comment.
Suggested change
| These changes are designed to make it clearer that you're not constrained to reactive programming when using these extensions. Whether you prefer a traditional blocking approach, reactive programming and/or virtual threads, Quarkus supports you. | |
| These changes are designed to make it clearer that you're not constrained to reactive programming when using these extensions. Whether you prefer a traditional blocking approach, reactive programming and/or virtual threads, Quarkus has you covered. |
|
@maxandersen I compiled the changes of @cescoffier and @geoand and added some additional content for you to review. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
still missing how to deal with quarkus-rest-client rename and clean up - so submitted as draft to at least get it going.
cc @gsmet @cescoffier @geoand