Introducing Quarkus Data Blog Post Final#2717
Conversation
|
@FroMage @yrodiere @maxandersen here's the final draft of the blog post, suggestions are welcome! I can't assign reviewers |
|
🙈 The PR is closed and the preview is expired. |
|
|
||
| == Try it today | ||
|
|
||
| You can try Quarkus Data Hibernate today from Quarkus 3.37.0. |
There was a problem hiding this comment.
We should probably publish this after we've renamed the types and packages? Hopefully this can be merged soon, but it will have to wait for 3.38 🤷
There was a problem hiding this comment.
I'd love it to publish it in these days, so 3.37 seems adeguate. I don't think renaming the classes makes such a difference... and besides it's alle experimental
There was a problem hiding this comment.
It is, it's just that it's likely people will feel pain with the rename, so more people looking at this means more angry users? Also, main and 3.37 is not what I showed in the Quarkus Insights (yet).
Otherwise, it's not overly problematic, so… as you wish 🤷
There was a problem hiding this comment.
Didn't you work on recipes to automatically handle the renaming in applications? Or did I misunderstand what those were for?
There was a problem hiding this comment.
Yeah, true. Well, Luca did for the module name. My rename PR doesn't yet have the recipes for the rename, but I should add them.
There was a problem hiding this comment.
If I'm not mistaken this blog post doesn't talk about specifics of the class names, so we can safely publish. The tutorial, on the other hand...
lucamolteni
force-pushed
the
39-blog-post
branch
from
de26753 to
ec23857
Compare
yrodiere
left a comment
yrodiere
left a comment
There was a problem hiding this comment.
Looks nice!
I added a few comments -- mostly about wording, so feel free to take what you agree with.
My main comment would be that you're very quick to declare that Quarkus Data solves the "many extensions" problem, while in fact it's just a start. See below.
| - **Active Record Pattern support**: entity lifecycle operations are on your entity by extending a simple class. The simplest way to get started. | ||
| - **Repositories**: define a standalone repository interface annotated with `@Repository`. The Hibernate annotation processor generates the implementation at compile time, with full type checking of queries and parameters against your entity model. | ||
| - **Stateless and Managed session**: Explicit lifecycles for simple cases, all the power of Hibernate managed objects when you need it. | ||
| - **Reactive**: The same entity model and project work in both blocking and non-blocking modes, useful when you need to interface with reactive code. |
There was a problem hiding this comment.
| - **Reactive**: The same entity model and project work in both blocking and non-blocking modes, useful when you need to interface with reactive code. | |
| - **Reactive**: The same entity model and project work in both blocking and non-blocking modes, useful when you need to integrate with reactive code. |
|
|
||
| == Try it today | ||
|
|
||
| You can try Quarkus Data Hibernate today from Quarkus 3.37.0. |
There was a problem hiding this comment.
Didn't you work on recipes to automatically handle the renaming in applications? Or did I misunderstand what those were for?
Yes but the new module name is from 3.37.0, or perhaps I'm missing what you mean by this |
lucamolteni
force-pushed
the
39-blog-post
branch
from
ec23857 to
0a1acee
Compare
3 participants
What comes next after #2662