(kafka) branch 4.1 updated: MINOR: Remove SPAM URL in Streams Documentation (#20321)

[mj...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

mjsax pushed a commit to branch 4.1
in repository https://gitbox.apache.org/repos/asf/kafka.git


The following commit(s) were added to refs/heads/4.1 by this push:
     new f61a5a5b41d MINOR: Remove SPAM URL in Streams Documentation (#20321)
f61a5a5b41d is described below

commit f61a5a5b41d7c15c285f9e6ec8b49af897500543
Author: Clemens Hutter <ch...@web.de>
AuthorDate: Fri Aug 8 11:17:36 2025 +0200

    MINOR: Remove SPAM URL in Streams Documentation (#20321)
    
    The previous URL http://lambda-architecture.net/ seems to now be controlled by spammers
    
    Co-authored-by: Shashank <hs...@gmail.com>
    Reviewers: Mickael Maison <mi...@gmail.com>
---
 docs/streams/core-concepts.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/streams/core-concepts.html b/docs/streams/core-concepts.html
index c400ca08453..a2d1b7209b5 100644
--- a/docs/streams/core-concepts.html
+++ b/docs/streams/core-concepts.html
@@ -279,7 +279,7 @@
     <p>
         In stream processing, one of the most frequently asked question is "does my stream processing system guarantee that each record is processed once and only once, even if some failures are encountered in the middle of processing?"
         Failing to guarantee exactly-once stream processing is a deal-breaker for many applications that cannot tolerate any data-loss or data duplicates, and in that case a batch-oriented framework is usually used in addition
-        to the stream processing pipeline, known as the <a href="http://lambda-architecture.net/">Lambda Architecture</a>.
+        to the stream processing pipeline, known as the <a href="https://en.wikipedia.org/wiki/Lambda_architecture">Lambda Architecture</a>.
         Prior to 0.11.0.0, Kafka only provides at-least-once delivery guarantees and hence any stream processing systems that leverage it as the backend storage could not guarantee end-to-end exactly-once semantics.
         In fact, even for those stream processing systems that claim to support exactly-once processing, as long as they are reading from / writing to Kafka as the source / sink, their applications cannot actually guarantee that
         no duplicates will be generated throughout the pipeline.<br />