shill for HR
This commit is contained in:
parent
85a156fd99
commit
05f4ac6483
|
@ -36,7 +36,7 @@ It's a simpler programming model, and lets the developer interact with the datab
|
|||
Stateful sessions certainly have their advantages, but they're more difficult to reason about, and when something goes wrong, the error messages can be more difficult to understand.
|
||||
====
|
||||
|
||||
[persistence-contexts]
|
||||
[[persistence-contexts]]
|
||||
=== Persistence Contexts
|
||||
|
||||
A persistence context is a sort of cache; we sometimes call it the "first-level cache", to distinguish it from the <<second-level-cache,second-level cache>>.
|
||||
|
|
|
@ -353,3 +353,13 @@ an entity is written to the database using
|
|||
| `PESSIMISTIC_FORCE_INCREMENT` | A pessimistic lock enforced using an immediate
|
||||
`update` to increment the version
|
||||
|===
|
||||
|
||||
[[hibernate-reactive]]
|
||||
=== Reactive programming with Hibernate
|
||||
|
||||
:hr: https://hibernate.org/reactive/
|
||||
:hr-guide: https://hibernate.org/reactive/documentation/2.0/reference/html_single/
|
||||
|
||||
Finally, many systems which require high scalability now make use of reactive programming and reactive streams.
|
||||
{hr}[Hibernate Reactive] brings O/R mapping to the world of reactive programming.
|
||||
You can learn much more about Hibernate Reactive from its {hr-guide}[Reference Documentation].
|
Loading…
Reference in New Issue