This is an automated email from the ASF dual-hosted git repository.
sjwiesman pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/flink-web.git
commit 5a8b85bd6c449ce4edebacf332568cd4b6845837
Author: sjwiesman <sjwies...@gmail.com>
AuthorDate: Wed Feb 16 17:37:28 2022 -0600
[FLINK-26200] Redirect statefun directly to docs
This closes #507
---
_includes/navbar.html | 4 +-
stateful-functions.md | 217 +---------------------------------------------
stateful-functions.zh.md | 218 +----------------------------------------------
3 files changed, 6 insertions(+), 433 deletions(-)
diff --git a/_includes/navbar.html b/_includes/navbar.html
index f3fc2bb..b6c9aaa 100755
--- a/_includes/navbar.html
+++ b/_includes/navbar.html
@@ -48,9 +48,9 @@
</ul>
{% endif %}
- <!-- What is Stateful Functions? -->
+ <!-- Stateful Functions? -->
- <li{% if page.url contains '/stateful-functions.html' %}
class="active"{% endif %}><a href="{{ baseurl_i18n
}}/stateful-functions.html">{{ site.data.i18n[page.language].what_is_statefun
}}</a></li>
+ <li><a
href="https://nightlies.apache.org/flink/flink-statefun-docs-stable/";>{{
site.data.i18n[page.language].what_is_statefun }}</a></li>
<!-- Use cases -->
<li{% if page.url contains '/usecases.html' %} class="active"{%
endif %}><a href="{{ baseurl_i18n }}/usecases.html">{{
site.data.i18n[page.language].use_case }}</a></li>
diff --git a/stateful-functions.md b/stateful-functions.md
index 383139a..0f98cd9 100644
--- a/stateful-functions.md
+++ b/stateful-functions.md
@@ -2,220 +2,7 @@
title: "Stateful Functions — Event-driven Applications on Apache Flink"
layout: base
---
-<div class="row-fluid">
- <div class="col-sm-12">
- <p class="lead" markdown="span">
- **Stateful Functions — Event-driven Applications on Apache
Flink<sup>®</sup>**
- </p>
- </div>
-<div class="col-sm-12">
- <hr />
-</div>
+This page has moved! If you are not automatically redirected follow this
[link](https://nightlies.apache.org/flink/flink-statefun-docs-stable/)
-</div>
-
-Stateful Functions is an API that **simplifies building distributed stateful
applications**. It's based on functions with persistent state that can interact
dynamically with strong consistency guarantees.
-
-<div style="line-height:60%;">
- <br>
-</div>
-
-<div class="row front-graphic">
- <img src="{{ site.baseurl }}/img/stateful-functions/statefun-overview.png"
width="650px"/>
-</div>
-
-### Stateful Functions Applications
-
-A _stateful function_ is a small piece of logic/code existing in multiple
instances that represent entities — similar to
[actors](https://www.brianstorti.com/the-actor-model/). Functions are invoked
through messages and are:
-
-<div class="jumbotron" style="height:auto;padding-top: 18px;padding-bottom:
12px;">
- <p style="font-size:100%;"><span class="glyphicon glyphicon
glyphicon-check"></span><b> Stateful</b></p>
- <p style="font-size:100%;">Functions have embedded, fault-tolerant state,
accessed locally like a variable.</p>
- <p style="font-size:100%;"><span class="glyphicon glyphicon
glyphicon-check"></span><b> Virtual</b></p>
- <p style="font-size:100%;">Much like FaaS, functions don't reserve resources
— inactive functions don't consume CPU/Memory.</p>
-</div>
-
-Applications are composed of _modules_ of multiple functions that can interact
arbitrarily with:
-
-<div class="jumbotron" style="height:auto;padding-top: 18px;padding-bottom:
12px;">
- <p style="font-size:100%;"><span class="glyphicon glyphicon
glyphicon-check"></span><b> Exactly-once Semantics</b></p>
- <p style="font-size:100%;">State and messaging go hand-in-hand, providing
exactly-once message/state semantics.</p>
- <p style="font-size:100%;"><span class="glyphicon glyphicon
glyphicon-check"></span><b> Logical Addressing</b></p>
- <p style="font-size:100%;">Functions message each other by logical
addresses. No service discovery needed.</p>
- <p style="font-size:100%;"><span class="glyphicon glyphicon
glyphicon-check"></span><b> Dynamic and Cyclic Messaging</b></p>
- <p style="font-size:100%;">Messaging patterns don't need to be pre-defined
as dataflows (<i>dynamic</i>) and are also not restricted to DAGs
(<i>cyclic</i>).</p>
-</div>
-
-<hr />
-
-## A Runtime built for Serverless Architectures
-
-The Stateful Functions runtime is designed to provide a set of properties
similar to what characterizes [serverless
functions](https://martinfowler.com/articles/serverless.html), but applied to
stateful problems.
-
-<div style="line-height:60%;">
- <br>
-</div>
-
-<!-- Remote Execution -->
-<div class="row front-graphic">
- <img src="{{ site.baseurl }}/img/stateful-functions/statefun-remote.png"
width="600px"/>
-</div>
-
-The runtime is built on Apache Flink<sup>®</sup>, with the following design
principles:
-
-<div class="jumbotron" style="height:auto;padding-top: 18px;padding-bottom:
12px;">
- <p style="font-size:100%;"><span class="glyphicon
glyphicon-edit"></span><b> Logical Compute/State Co-location:</b></p>
- <p style="font-size:100%;">Messaging, state access/updates and function
invocations are managed tightly together. This ensures a high-level of
consistency out-of-the-box.</p>
- <p style="font-size:100%;"><span class="glyphicon
glyphicon-edit"></span><b> Physical Compute/State Separation:</b></p>
- <p style="font-size:100%;">Functions can be executed remotely, with
message and state access provided as part of the invocation request. This way,
functions can be managed like stateless processes and support rapid scaling,
rolling upgrades and other common operational patterns.</p>
- <p style="font-size:100%;"><span class="glyphicon
glyphicon-edit"></span><b> Language Independence:</b></p>
- <p style="font-size:100%;">Function invocations use a simple
HTTP/gRPC-based protocol so that Functions can be easily implemented in various
languages.</p>
-</div>
-
-This makes it possible to execute functions on a **Kubernetes deployment**, a
**FaaS platform** or **behind a (micro)service**, while providing consistent
state and lightweight messaging between functions.
-
-<hr />
-
-## Key Benefits
-
-<div style="line-height:60%;">
- <br>
-</div>
-
-<!-- Product Marketing Properties -->
-<div class="row">
- <!-- Arbitrary Messaging -->
- <div class="col-lg-4">
- <div class="text-center">
- <img class="img-circle" src="{{ site.baseurl
}}/img/stateful-functions/statefun-prop3.png" alt="Arbitrary Messaging"
width="90" height="90">
- <h3>Dynamic Messaging</h3>
- </div>
- <p align="justify">The API allows you to build and compose functions that
communicate dynamic- and arbitrarily with each other. This gives you much more
flexibility compared to the acyclic nature of classical stream processing
topologies.</p>
- <p align="justify"><a
href="{{site.DOCS_BASE_URL}}flink-statefun-docs-release-3.0/docs/concepts/application-building-blocks#stateful-functions">Learn
More</a></p>
- </div>
- <!-- Consistent State -->
- <div class="col-lg-4">
- <div class="text-center">
- <img class="img-circle" src="{{ site.baseurl
}}/img/stateful-functions/statefun-prop1.png" alt="Consistent State" width="90"
height="90">
- <h3>Consistent State</h3>
- <p align="justify">Functions can keep local state that is persistent and
integrated with the messaging between functions. This gives you the effect of
exactly-once state access/updates and guaranteed efficient messaging
out-of-the-box.</p>
- <p align="justify"><a
href="{{site.DOCS_BASE_URL}}flink-statefun-docs-release-3.0/docs/concepts/application-building-blocks#persisted-states">Learn
More</a></p>
- </div>
- </div>
- <!-- Multi-language Support -->
- <div class="col-lg-4">
- <div class="text-center">
- <img class="img-circle" src="{{ site.baseurl
}}/img/stateful-functions/statefun-prop4.png" alt="Multi-language Support"
width="90" height="90">
- <h3>Multi-language Support</h3>
- </div>
- <p align="justify">Functions can be implemented in any programming
language that can handle HTTP requests or bring up a gRPC server, with initial
support for Python. More SDKs will be added for languages like Go, Javascript
and Rust.
- </p>
- <p align="justify"><a
href="{{site.DOCS_BASE_URL}}flink-statefun-docs-stable/docs/concepts/distributed_architecture/#remote-functions">Learn
More</a></p>
- </div>
-</div>
-
-<hr />
-
-<div class="row">
- <!-- No Database Required -->
- <div class="col-lg-4">
- <div class="text-center">
- <img class="img-circle" src="{{ site.baseurl
}}/img/stateful-functions/statefun-prop5.png" alt="No Database Required"
width="90" height="90">
- <h3>No Database Required</h3>
- </div>
- <p align="justify">State durability and fault tolerance build on Apache
Flink’s robust distributed snapshots model. This requires nothing but a simple
blob storage tier (e.g. S3, GCS, HDFS) to store the state snapshots.</p>
- <p align="justify"><a
href="{{site.DOCS_BASE_URL}}flink-docs-stable/learn-flink/fault_tolerance.html">Learn
More</a></p>
- </div>
- <!-- Cloud Native -->
- <div class="col-lg-4">
- <div class="text-center">
- <img class="img-circle" src="{{ site.baseurl
}}/img/stateful-functions/statefun-prop6.png" alt="Ecosystem Integration"
width="90" height="90">
- <h3>Cloud Native</h3>
- </div>
- <p align="justify">Stateful Function's approach to state and composition
can be combined with the capabilities of modern serverless platforms like
Kubernetes, Knative and AWS Lambda.</p>
- <p align="justify"
href="https://thenewstack.io/10-key-attributes-of-cloud-native-applications/";><a
href="">Learn More</a></p>
- </div>
- <!-- "Stateless" Operation -->
- <div class="col-lg-4">
- <div class="text-center">
- <img class="img-circle" src="{{ site.baseurl
}}/img/stateful-functions/statefun-prop2.png" alt="Stateless Operation"
width="90" height="90">
- <h3>"Stateless" Operation</h3>
- </div>
- <p align="justify">State access is part of the function invocation and so
Stateful Functions applications behave like stateless processes that can be
managed with the same simplicity and benefits, like rapid scalability,
scale-to-zero and rolling/zero-downtime upgrades.
- </p>
- <p align="justify"><a
href="{{site.DOCS_BASE_URL}}flink-statefun-docs-stable/docs/deployment/module/">Learn
More</a></p>
- </div>
-</div>
-
-<hr />
-
-## An Example: Transaction Scoring for Fraud Detection
-
-<div style="line-height:60%;">
- <br>
-</div>
-
-<div class="row">
- <div class="col-sm-5">
- <img src="{{ site.baseurl }}/img/stateful-functions/model-score.svg"
width="400px"/>
- </div>
- <div class="col-sm-7">
- <p>Imagine an application that receives financial information and emits
alerts for every transaction that exceeds a given threshold fraud score (i.e.
fraudulent). To build this example with <b>Stateful Functions</b>, you can
define four different functions, each tracking its own state:</p>
- <p><b>Fraud Count:</b> tracks the total number of reported fraudulent
transactions made against an account on a rolling 30 day period.</p>
- <p><b>Merchant Scorer:</b> returns a trustworthiness score for each
merchant, relying on a third party service.</p>
- <p><b>Transaction Manager:</b> enriches transaction records to create
feature vectors for scoring and emits fraud alert events.</b></p>
- <p><b>Model:</b> scores transactions based on input feature vectors
from the Transaction Manager.</p>
- </div>
-</div>
-
-<div style="line-height:60%;">
- <br>
-</div>
-
-**Keeping track of fraudulent reports**
-
-The entry points to the application are the "Fraud Confirmation" and
"Transactions"
[_ingresses_]({{site.DOCS_BASE_URL}}flink-statefun-docs-stable/concepts/application-building-blocks.html#event-ingress)
(e.g. Kafka Topics). As events flow in from "Fraud Confirmation", the "Fraud
Count" function increments its internal counter and sets a 30-day expiration
timer on this state. Here, multiple instances of "Fraud Count" will exist — for
example, one per customer account. After 30 days, the [...]
-
-**Enriching and scoring transactions**
-
-On receiving events from the "Transactions" ingress, the "Transaction Manager"
function messages "Fraud Count" to get the current count of fraud cases
reported for the customer account; it also messages the "Merchant Scorer" for
the trustworthiness score of the transaction merchant. "Transaction Manager"
creates a feature vector with the count of fraud cases reported and the
merchant score for the customer account that is then sent to the "Model"
function for scoring.
-
-**Emitting alerts**
-
-Depending on the score sent back to "Transaction Manager", it may emit an
alert event to the "Alert User"
[_egress_]({{site.DOCS_BASE_URL}}flink-statefun-docs-stable/concepts/application-building-blocks.html#event-egress)
if a given threshold is exceeded.
-
-<hr />
-
-## Learn More
-
-If you find these ideas interesting, give Stateful Functions a try and get
involved! Check out the [Getting
Started]({{site.DOCS_BASE_URL}}flink-statefun-docs-stable/getting-started/project-setup.html)
section for introduction walkthroughs and the
[documentation]({{site.DOCS_BASE_URL}}flink-statefun-docs-stable/) for a deeper
look into the internals of Stateful Functions.
-
-<div style="line-height:60%;">
- <br>
-</div>
-
-<a href="https://github.com/apache/flink-statefun";><img src="{{ site.baseurl
}}/img/stateful-functions/github-logo-link.png" class="rounded-circle"
width="20px" height="20px"></a> <small>GitHub Repository</small>
-
-<a href="{{site.DOCS_BASE_URL}}flink-statefun-docs-stable/"><img src="{{
site.baseurl }}/img/stateful-functions/favicon.png" class="rounded-circle"
width="20px" height="20px"></a> <small>StateFun Documentation</small>
-
-<a href="https://twitter.com/statefun_io";><img src="{{ site.baseurl
}}/img/stateful-functions/twitter-logo-link.png" class="rounded-circle"
width="20px" height="20px"></a> <small>StateFun Twitter</small>
-
-<!-- Gimmick to make the last link work -->
-<a href="https://twitter.com/statefun_io";><img src="{{ site.baseurl
}}/img/stateful-functions/twitter-logo-link.png" class="rounded-circle"
width="0px" height="0px"></a> <small></small>
-
-<hr />
-
-<div class="row">
- <div class="col-sm-5">
- <h3>For a quick overview,</h3>
- watch <a href="https://youtu.be/fCeHCMJXXM0";>this whiteboard session</a>.
- </div>
- <div class="col-sm-7">
- <div class="bs-example"
data-example-id="responsive-embed-16by9-iframe-youtube">
- <div class="embed-responsive embed-responsive-16by9">
- <iframe class="embed-responsive-item"
src="https://www.youtube.com/embed/fCeHCMJXXM0"; allowfullscreen></iframe>"
allowfullscreen></iframe>
- </div>
- </div>
- </div>
-</div>
+<meta http-equiv="refresh" content="0;
url=https://nightlies.apache.org/flink/flink-statefun-docs-stable/"; />
diff --git a/stateful-functions.zh.md b/stateful-functions.zh.md
index 288210a..7405ece 100644
--- a/stateful-functions.zh.md
+++ b/stateful-functions.zh.md
@@ -2,220 +2,6 @@
title: "Stateful Functions — Event-driven Applications on Apache Flink"
layout: base
---
-<div class="row-fluid">
+This page has moved! If you are not automatically redirected follow this
[link](https://nightlies.apache.org/flink/flink-statefun-docs-stable/)
- <div class="col-sm-12">
- <p class="lead" markdown="span">
- **Stateful Functions — Event-driven Applications on Apache
Flink<sup>®</sup>**
- </p>
- </div>
-<div class="col-sm-12">
- <hr />
-</div>
-
-</div>
-
-Stateful Functions is an API that **simplifies building distributed stateful
applications**. It's based on functions with persistent state that can interact
dynamically with strong consistency guarantees.
-
-<div style="line-height:60%;">
- <br>
-</div>
-
-<div class="row front-graphic">
- <img src="{{ site.baseurl }}/img/stateful-functions/statefun-overview.png"
width="650px"/>
-</div>
-
-### Stateful Functions Applications
-
-A _stateful function_ is a small piece of logic/code existing in multiple
instances that represent entities — similar to
[actors](https://www.brianstorti.com/the-actor-model/). Functions are invoked
through messages and are:
-
-<div class="jumbotron" style="height:auto;padding-top: 18px;padding-bottom:
12px;">
- <p style="font-size:100%;"><span class="glyphicon glyphicon
glyphicon-check"></span><b> Stateful</b></p>
- <p style="font-size:100%;">Functions have embedded, fault-tolerant state,
accessed locally like a variable.</p>
- <p style="font-size:100%;"><span class="glyphicon glyphicon
glyphicon-check"></span><b> Virtual</b></p>
- <p style="font-size:100%;">Much like FaaS, functions don't reserve resources
— inactive functions don't consume CPU/Memory.</p>
-</div>
-
-Applications are composed of _modules_ of multiple functions that can interact
arbitrarily with:
-
-<div class="jumbotron" style="height:auto;padding-top: 18px;padding-bottom:
12px;">
- <p style="font-size:100%;"><span class="glyphicon glyphicon
glyphicon-check"></span><b> Exactly-once Semantics</b></p>
- <p style="font-size:100%;">State and messaging go hand-in-hand, providing
exactly-once message/state semantics.</p>
- <p style="font-size:100%;"><span class="glyphicon glyphicon
glyphicon-check"></span><b> Logical Addressing</b></p>
- <p style="font-size:100%;">Functions message each other by logical
addresses. No service discovery needed.</p>
- <p style="font-size:100%;"><span class="glyphicon glyphicon
glyphicon-check"></span><b> Dynamic and Cyclic Messaging</b></p>
- <p style="font-size:100%;">Messaging patterns don't need to be pre-defined
as dataflows (<i>dynamic</i>) and are also not restricted to DAGs
(<i>cyclic</i>).</p>
-</div>
-
-<hr />
-
-## A Runtime built for Serverless Architectures
-
-The Stateful Functions runtime is designed to provide a set of properties
similar to what characterizes [serverless
functions](https://martinfowler.com/articles/serverless.html), but applied to
stateful problems.
-
-<div style="line-height:60%;">
- <br>
-</div>
-
-<!-- Remote Execution -->
-<div class="row front-graphic">
- <img src="{{ site.baseurl }}/img/stateful-functions/statefun-remote.png"
width="600px"/>
-</div>
-
-The runtime is built on Apache Flink<sup>®</sup>, with the following design
principles:
-
-<div class="jumbotron" style="height:auto;padding-top: 18px;padding-bottom:
12px;">
- <p style="font-size:100%;"><span class="glyphicon
glyphicon-edit"></span><b> Logical Compute/State Co-location:</b></p>
- <p style="font-size:100%;">Messaging, state access/updates and function
invocations are managed tightly together. This ensures a high-level of
consistency out-of-the-box.</p>
- <p style="font-size:100%;"><span class="glyphicon
glyphicon-edit"></span><b> Physical Compute/State Separation:</b></p>
- <p style="font-size:100%;">Functions can be executed remotely, with
message and state access provided as part of the invocation request. This way,
functions can be managed like stateless processes and support rapid scaling,
rolling upgrades and other common operational patterns.</p>
- <p style="font-size:100%;"><span class="glyphicon
glyphicon-edit"></span><b> Language Independence:</b></p>
- <p style="font-size:100%;">Function invocations use a simple
HTTP/gRPC-based protocol so that Functions can be easily implemented in various
languages.</p>
-</div>
-
-This makes it possible to execute functions on a **Kubernetes deployment**, a
**FaaS platform** or **behind a (micro)service**, while providing consistent
state and lightweight messaging between functions.
-
-<hr />
-
-## Key Benefits
-
-<div style="line-height:60%;">
- <br>
-</div>
-
-<!-- Product Marketing Properties -->
-<div class="row">
- <!-- Arbitrary Messaging -->
- <div class="col-lg-4">
- <div class="text-center">
- <img class="img-circle" src="{{ site.baseurl
}}/img/stateful-functions/statefun-prop3.png" alt="Arbitrary Messaging"
width="90" height="90">
- <h3>Dynamic Messaging</h3>
- </div>
- <p align="justify">The API allows you to build and compose functions that
communicate dynamic- and arbitrarily with each other. This gives you much more
flexibility compared to the acyclic nature of classical stream processing
topologies.</p>
- <p align="justify"><a
href="{{site.DOCS_BASE_URL}}flink-statefun-docs-release-3.0/docs/concepts/application-building-blocks#stateful-functions">Learn
More</a></p>
- </div>
- <!-- Consistent State -->
- <div class="col-lg-4">
- <div class="text-center">
- <img class="img-circle" src="{{ site.baseurl
}}/img/stateful-functions/statefun-prop1.png" alt="Consistent State" width="90"
height="90">
- <h3>Consistent State</h3>
- <p align="justify">Functions can keep local state that is persistent and
integrated with the messaging between functions. This gives you the effect of
exactly-once state access/updates and guaranteed efficient messaging
out-of-the-box.</p>
- <p align="justify"><a
href="{{site.DOCS_BASE_URL}}flink-statefun-docs-release-3.0/docs/concepts/application-building-blocks#persisted-states">Learn
More</a></p>
- </div>
- </div>
- <!-- Multi-language Support -->
- <div class="col-lg-4">
- <div class="text-center">
- <img class="img-circle" src="{{ site.baseurl
}}/img/stateful-functions/statefun-prop4.png" alt="Multi-language Support"
width="90" height="90">
- <h3>Multi-language Support</h3>
- </div>
- <p align="justify">Functions can be implemented in any programming
language that can handle HTTP requests or bring up a gRPC server, with initial
support for Python. More SDKs will be added for languages like Go, Javascript
and Rust.
- </p>
- <p align="justify"><a
href="{{site.DOCS_BASE_URL}}flink-statefun-docs-stable/docs/concepts/distributed_architecture/#remote-functions">Learn
More</a></p>
- </div>
-</div>
-
-<hr />
-
-<div class="row">
- <!-- No Database Required -->
- <div class="col-lg-4">
- <div class="text-center">
- <img class="img-circle" src="{{ site.baseurl
}}/img/stateful-functions/statefun-prop5.png" alt="No Database Required"
width="90" height="90">
- <h3>No Database Required</h3>
- </div>
- <p align="justify">State durability and fault tolerance build on Apache
Flink’s robust distributed snapshots model. This requires nothing but a simple
blob storage tier (e.g. S3, GCS, HDFS) to store the state snapshots.</p>
- <p align="justify"><a
href="{{site.DOCS_BASE_URL}}flink-docs-stable/learn-flink/fault_tolerance.html">Learn
More</a></p>
- </div>
- <!-- Cloud Native -->
- <div class="col-lg-4">
- <div class="text-center">
- <img class="img-circle" src="{{ site.baseurl
}}/img/stateful-functions/statefun-prop6.png" alt="Ecosystem Integration"
width="90" height="90">
- <h3>Cloud Native</h3>
- </div>
- <p align="justify">Stateful Function's approach to state and composition
can be combined with the capabilities of modern serverless platforms like
Kubernetes, Knative and AWS Lambda.</p>
- <p align="justify"
href="https://thenewstack.io/10-key-attributes-of-cloud-native-applications/";><a
href="">Learn More</a></p>
- </div>
- <!-- "Stateless" Operation -->
- <div class="col-lg-4">
- <div class="text-center">
- <img class="img-circle" src="{{ site.baseurl
}}/img/stateful-functions/statefun-prop2.png" alt="Stateless Operation"
width="90" height="90">
- <h3>"Stateless" Operation</h3>
- </div>
- <p align="justify">State access is part of the function invocation and so
Stateful Functions applications behave like stateless processes that can be
managed with the same simplicity and benefits, like rapid scalability,
scale-to-zero and rolling/zero-downtime upgrades.
- </p>
- <p align="justify"><a
href="{{site.DOCS_BASE_URL}}flink-statefun-docs-stable/docs/deployment/module/">Learn
More</a></p>
- </div>
-</div>
-
-<hr />
-
-## An Example: Transaction Scoring for Fraud Detection
-
-<div style="line-height:60%;">
- <br>
-</div>
-
-<div class="row">
- <div class="col-sm-5">
- <img src="{{ site.baseurl }}/img/stateful-functions/model-score.svg"
width="350px"/>
- </div>
- <div class="col-sm-7">
- <p>Imagine an application that receives financial information and emits
alerts for every transaction that exceeds a given threshold fraud score (i.e.
fraudulent). To build this example with <b>Stateful Functions</b>, you can
define four different functions, each tracking its own state:</p>
- <p><b>Fraud Count:</b> tracks the total number of reported fraudulent
transactions made against an account on a rolling 30 day period.</p>
- <p><b>Merchant Scorer:</b> returns a trustworthiness score for each
merchant, relying on a third party service.</p>
- <p><b>Transaction Manager:</b> enriches transaction records to create
feature vectors for scoring and emits fraud alert events.</b></p>
- <p><b>Model:</b> scores transactions based on input feature vectors
from the Transaction Manager.</p>
- </div>
-</div>
-
-<div style="line-height:60%;">
- <br>
-</div>
-
-**Keeping track of fraudulent reports**
-
-The entry points to the application are the "Fraud Confirmation" and
"Transactions"
[_ingresses_]({{site.DOCS_BASE_URL}}flink-statefun-docs-stable/concepts/application-building-blocks.html#event-ingress)
(e.g. Kafka Topics). As events flow in from "Fraud Confirmation", the "Fraud
Count" function increments its internal counter and sets a 30-day expiration
timer on this state. Here, multiple instances of "Fraud Count" will exist — for
example, one per customer account. After 30 days, the [...]
-
-**Enriching and scoring transactions**
-
-On receiving events from the "Transactions" ingress, the "Transaction Manager"
function messages "Fraud Count" to get the current count of fraud cases
reported for the customer account; it also messages the "Merchant Scorer" for
the trustworthiness score of the transaction merchant. "Transaction Manager"
creates a feature vector with the count of fraud cases reported and the
merchant score for the customer account that is then sent to the "Model"
function for scoring.
-
-**Emitting alerts**
-
-Depending on the score sent back to "Transaction Manager", it may emit an
alert event to the "Alert User"
[_egress_]({{site.DOCS_BASE_URL}}flink-statefun-docs-stable/concepts/application-building-blocks.html#event-egress)
if a given threshold is exceeded.
-
-<hr />
-
-## Learn More
-
-If you find these ideas interesting, give Stateful Functions a try and get
involved! Check out the [Getting
Started]({{site.DOCS_BASE_URL}}flink-statefun-docs-stable/getting-started/project-setup.html)
section for introduction walkthroughs and the
[documentation]({{site.DOCS_BASE_URL}}flink-statefun-docs-stable/) for a deeper
look into the internals of Stateful Functions.
-
-<div style="line-height:60%;">
- <br>
-</div>
-
-<a href="https://github.com/apache/flink-statefun";><img src="{{ site.baseurl
}}/img/stateful-functions/github-logo-link.png" class="rounded-circle"
width="20px" height="20px"></a> <small>GitHub Repository</small>
-
-<a href="{{site.DOCS_BASE_URL}}flink-statefun-docs-stable/"><img src="{{
site.baseurl }}/img/stateful-functions/favicon.png" class="rounded-circle"
width="20px" height="20px"></a> <small>StateFun Documentation</small>
-
-<a href="https://twitter.com/statefun_io";><img src="{{ site.baseurl
}}/img/stateful-functions/twitter-logo-link.png" class="rounded-circle"
width="20px" height="20px"></a> <small>StateFun Twitter</small>
-
-<!-- Gimmick to make the last link work -->
-<a href="https://twitter.com/statefun_io";><img src="{{ site.baseurl
}}/img/stateful-functions/twitter-logo-link.png" class="rounded-circle"
width="0px" height="0px"></a> <small></small>
-
-<hr />
-
-<div class="row">
- <div class="col-sm-5">
- <h3>For a quick overview,</h3>
- watch <a href="https://youtu.be/fCeHCMJXXM0";>this whiteboard session</a>.
- </div>
- <div class="col-sm-7">
- <div class="bs-example"
data-example-id="responsive-embed-16by9-iframe-youtube">
- <div class="embed-responsive embed-responsive-16by9">
- <iframe class="embed-responsive-item"
src="https://www.youtube.com/embed/fCeHCMJXXM0"; allowfullscreen></iframe>"
allowfullscreen></iframe>
- </div>
- </div>
- </div>
-</div>
+<meta http-equiv="refresh" content="0;
url=https://nightlies.apache.org/flink/flink-statefun-docs-stable/"; />
\ No newline at end of file
