You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/src/main/paradox/persistence-query.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -202,7 +202,7 @@ Java
202
202
203
203
## Performance and denormalization
204
204
205
-
When building systems using @ref:[Event Sourcing](typed/persistence.md#event-sourcing-concepts) and CQRS ([Command & Query Responsibility Segregation](https://docs.microsoft.com/en-us/previous-versions/msp-n-p/jj554200%28v=pandp.10%29)) techniques
205
+
When building systems using @ref:[Event Sourcing](typed/persistence.md#event-sourcing-concepts) and CQRS ([Command & Query Responsibility Segregation](https://learn.microsoft.com/en-us/previous-versions/msp-n-p/jj554200%28v=pandp.10%29)) techniques
206
206
it is tremendously important to realise that the write-side has completely different needs from the read-side,
207
207
and separating those concerns into datastores that are optimised for either side makes it possible to offer the best
208
208
experience for the write and read sides independently.
Copy file name to clipboardExpand all lines: docs/src/main/paradox/persistence-schema-evolution.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ evolution feel free to submit Pull Requests to this page to extend it.
45
45
46
46
In recent years we have observed a tremendous move towards immutable append-only datastores, with event-sourcing being
47
47
the prime technique successfully being used in these settings. For an excellent overview why and how immutable data makes scalability
48
-
and systems design much simpler you may want to read Pat Helland's excellent [Immutability Changes Everything](http://cidrdb.org/cidr2015/Papers/CIDR15_Paper16.pdf) whitepaper.
48
+
and systems design much simpler you may want to read Pat Helland's excellent [Immutability Changes Everything](https://cidrdb.org/cidr2015/Papers/CIDR15_Paper16.pdf) whitepaper.
49
49
50
50
Since with [Event Sourcing](https://martinfowler.com/eaaDev/EventSourcing.html) the **events are immutable** and usually never deleted – the way schema evolution is handled
51
51
differs from how one would go about it in a mutable database setting (e.g. in typical CRUD database applications).
Copy file name to clipboardExpand all lines: docs/src/main/paradox/typed/failure-detector.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@
5
5
Remote DeathWatch uses heartbeat messages and the failure detector to detect network failures and JVM crashes.
6
6
7
7
The heartbeat arrival times are interpreted by an implementation of
8
-
[The Phi Accrual Failure Detector](https://pdfs.semanticscholar.org/11ae/4c0c0d0c36dc177c1fff5eb84fa49aa3e1a8.pdf) by Hayashibara et al.
8
+
[The Phi Accrual Failure Detector](https://www.semanticscholar.org/paper/The-spl-phi-accrual-failure-detector-Hayashibara-D%C3%A9fago/11ae4c0c0d0c36dc177c1fff5eb84fa49aa3e1a8?p2df) by Hayashibara et al.
0 commit comments