This is an automated email from the ASF dual-hosted git repository.
fanningpj pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/pekko.git
The following commit(s) were added to refs/heads/main by this push:
new 97d900327f replace broken link to Ben Christensen talk (#2489)
97d900327f is described below
commit 97d900327f2e7e52a5675708b1631964424e88c8
Author: PJ Fanning <[email protected]>
AuthorDate: Wed Nov 12 23:15:42 2025 +0100
replace broken link to Ben Christensen talk (#2489)
---
docs/src/main/paradox/typed/choosing-cluster.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/src/main/paradox/typed/choosing-cluster.md
b/docs/src/main/paradox/typed/choosing-cluster.md
index 88c7ab6ee6..90c06f4f53 100644
--- a/docs/src/main/paradox/typed/choosing-cluster.md
+++ b/docs/src/main/paradox/typed/choosing-cluster.md
@@ -59,7 +59,7 @@ very risky, such as a shared cluster, shared code and
dependencies for service A
database schema. There is a false sense of autonomy because of the physical
separation of the code and
deployment units, but you are likely to encounter problems because of changes
in the implementation of
one service leaking into the behavior of others. See Ben Christensen's
-[Don’t Build a Distributed
Monolith](https://www.microservices.com/talks/dont-build-a-distributed-monolith/).
+[Don’t Build a Distributed
Monolith](https://www.slideshare.net/slideshow/avoid-distributed-monoliths/58636003).
Organizations that find themselves in this situation often react by trying to
centrally coordinate deployment
of multiple services, at which point you have lost the principal benefit of
microservices while taking on
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
