[flink] branch release-1.11 updated: [hotfix] Remove section about as-a-library from flink-architecture.md

[aljoscha]

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

aljoscha pushed a commit to branch release-1.11
in repository https://gitbox.apache.org/repos/asf/flink.git


The following commit(s) were added to refs/heads/release-1.11 by this push:
     new 7e64f64  [hotfix] Remove section about as-a-library from 
flink-architecture.md
7e64f64 is described below

commit 7e64f64f3eeda01d552f27e8238abccdb07590a2
Author: Aljoscha Krettek <aljos...@apache.org>
AuthorDate: Mon Jul 6 15:28:41 2020 +0200

    [hotfix] Remove section about as-a-library from flink-architecture.md
    
    This describes possible future work and partially the described
    functionality is already available with application mode.
---
 docs/concepts/flink-architecture.md    | 15 ---------------
 docs/concepts/flink-architecture.zh.md | 15 ---------------
 2 files changed, 30 deletions(-)

diff --git a/docs/concepts/flink-architecture.md 
b/docs/concepts/flink-architecture.md
index 2862752..578e809 100644
--- a/docs/concepts/flink-architecture.md
+++ b/docs/concepts/flink-architecture.md
@@ -250,18 +250,3 @@ isolation guarantees.
 <div class="alert alert-info"> <strong>Note:</strong> A Flink Job Cluster can 
be seen as a “run-on-client” alternative to Flink Application Clusters. </div>
 
 {% top %}
-
-## Self-contained Flink Applications
-
-When you want to create and deploy something like an event-driven application, 
it doesn’t make
-sense that you have to think about and manage a cluster. So, there are efforts
-in the community towards fully enabling _Flink-as-a-Library_ in the future.
-
-The idea is that deploying a Flink Application becomes as easy as starting a
-process: Flink would be like any other library which you add to your 
application, with no effect on how you deploy it. When you want to deploy such 
an
-application, it simply starts a set of processes which connect to each other,
-figure out their roles (e.g. JobManager, TaskManager) and execute the
-application in a distributed, parallel way. If the application cannot keep up
-with the workload, Flink automatically starts new processes to rescale (i.e. 
auto-scaling).
-
-{% top %}
diff --git a/docs/concepts/flink-architecture.zh.md 
b/docs/concepts/flink-architecture.zh.md
index c11bb4f..1615c14 100644
--- a/docs/concepts/flink-architecture.zh.md
+++ b/docs/concepts/flink-architecture.zh.md
@@ -250,18 +250,3 @@ isolation guarantees.
 <div class="alert alert-info"> <strong>Note:</strong> A Flink Job Cluster can 
be seen as a “run-on-client” alternative to Flink Application Clusters. </div>
 
 {% top %}
-
-## Self-contained Flink Applications
-
-When you want to create and deploy something like an event-driven application, 
it doesn’t make
-sense that you have to think about and manage a cluster. So, there are efforts
-in the community towards fully enabling _Flink-as-a-Library_ in the future.
-
-The idea is that deploying a Flink Application becomes as easy as starting a
-process: Flink would be like any other library which you add to your 
application, with no effect on how you deploy it. When you want to deploy such 
an
-application, it simply starts a set of processes which connect to each other,
-figure out their roles (e.g. JobManager, TaskManager) and execute the
-application in a distributed, parallel way. If the application cannot keep up
-with the workload, Flink automatically starts new processes to rescale (i.e. 
auto-scaling).
-
-{% top %}