From f730e16fb47b0fcace7d3a1a8c8e3cb2c837ceec Mon Sep 17 00:00:00 2001 From: Aljoscha Krettek Date: Mon, 6 Jul 2020 15:28:41 +0200 Subject: [PATCH] [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 2862752f392a4..578e809ee88f8 100644 --- a/docs/concepts/flink-architecture.md +++ b/docs/concepts/flink-architecture.md @@ -250,18 +250,3 @@ isolation guarantees.
Note: A Flink Job Cluster can be seen as a “run-on-client” alternative to Flink Application Clusters.
{% 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 c11bb4fd6abc9..1615c14804720 100644 --- a/docs/concepts/flink-architecture.zh.md +++ b/docs/concepts/flink-architecture.zh.md @@ -250,18 +250,3 @@ isolation guarantees.
Note: A Flink Job Cluster can be seen as a “run-on-client” alternative to Flink Application Clusters.
{% 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 %}