sjwiesman commented on a change in pull request #95: [FLINK-16977][docs] Add docs for components and distributed architecture URL: https://github.com/apache/flink-statefun/pull/95#discussion_r403198004
########## File path: docs/concepts/distributed_architecture.md ########## @@ -0,0 +1,99 @@ +--- +title: Distributed Architecture +nav-id: dist-arch +nav-pos: 2 +nav-title: Architecture +nav-parent_id: concepts +--- +<!-- +Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. +--> + +A Stateful Functions deployment consists of a few components interacting together. Here we describe these pieces and their + +* This will be replaced by the TOC +{:toc} + +## High-level View + +A *Stateful Functions* deployment consists of a set of **Apache Flink Stateful Functions** processes and, optionally, various deployments that execute remote functions. + +<p class="text-center"> + <img width="80%" src="{{ site.baseurl }}/fig/concepts/arch_overview.svg"/> +</p> + +The Flink worker processes (TaskManagers) receive the events from the ingress systems (Kafka, Kinesis, etc.) and route them to the target functions. They invoke the functions, and route the resulting mesages to the next respective target functions. Messages designated for egress are written to an egress system (again, Kafka, Kinesis, ...). Review comment: ```suggestion The Flink worker processes (TaskManagers) receive the events from the ingress systems (Kafka, Kinesis, etc.) and route them to the target functions. They invoke the functions and route the resulting messages to the next respective target functions. Messages designated for egress are written to an egress system (again, Kafka, Kinesis, ...). ``` ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
