morsapaes commented on a change in pull request #132:
URL: https://github.com/apache/flink-statefun/pull/132#discussion_r472022178
##########
File path: docs/index.md
##########
@@ -23,16 +23,16 @@ specific language governing permissions and limitations
under the License.
-->
-**Stateful Functions** is an open source framework that reduces the complexity
of building and orchestrating distributed stateful applications at scale.
-It brings together the benefits of stream processing with Apache Flink® and
Function-as-a-Service (FaaS) to provide a powerful abstraction for the next
generation of event-driven architectures.
+**Stateful Functions** is a framework, developed under the umbrella of Apache
Flink, that makes it simple to build **consistent stateful serverless
applications**.
Review comment:
I think here we're going from concepts people can relate to to a
mouthful of buzzwords, to be honest. "Stateful serverless" is good to create
hype for conferences and such, but I don't think the people who might use
StateFun will relate to that more than to "this is like if you bring what's
good in stateful stream processing and FaaS together".
##########
File path: docs/index.md
##########
@@ -23,16 +23,16 @@ specific language governing permissions and limitations
under the License.
-->
-**Stateful Functions** is an open source framework that reduces the complexity
of building and orchestrating distributed stateful applications at scale.
-It brings together the benefits of stream processing with Apache Flink® and
Function-as-a-Service (FaaS) to provide a powerful abstraction for the next
generation of event-driven architectures.
+**Stateful Functions** is a framework, developed under the umbrella of Apache
Flink, that makes it simple to build **consistent stateful serverless
applications**.
+It is designed to work with modern architectures, like stateless Kubernetes
deployments or popular event-driven FaaS platforms like AWS Lambda, KNative,
etc.,
+to provide out-of-the-box consistent state and messaging to preserve the
serverless experience and elasticity of these platforms.
<p class="text-center">
- <img width="80%" src="{{ site.baseurl }}/fig/stateful_functions.png"/>
+ <img width="80%" src="{{ site.baseurl }}/fig/concepts/arch_overview.svg"/>
</p>
-There are many ways to get started with Stateful Functions.
-Which one is the best for you depends on your goals and prior experience.
-Whether you prefer a more theoretical or a practical approach, we hope you’ll
find this section helpful.
+It brings together the benefits of Apache Flink®, streaming semantics for
processing large datasets with low latency and bounded resource constraints,
+along with a runtime for modeling stateful entities that supports location
transparency, concurrency, scaling, and resiliency.
Review comment:
```suggestion
along with a runtime for modeling stateful entities that supports location
transparency, concurrency, scaling, and resilience.
```
##########
File path: docs/index.md
##########
@@ -23,16 +23,16 @@ specific language governing permissions and limitations
under the License.
-->
-**Stateful Functions** is an open source framework that reduces the complexity
of building and orchestrating distributed stateful applications at scale.
-It brings together the benefits of stream processing with Apache Flink® and
Function-as-a-Service (FaaS) to provide a powerful abstraction for the next
generation of event-driven architectures.
+**Stateful Functions** is a framework, developed under the umbrella of Apache
Flink, that makes it simple to build **consistent stateful serverless
applications**.
+It is designed to work with modern architectures, like stateless Kubernetes
deployments or popular event-driven FaaS platforms like AWS Lambda, KNative,
etc.,
Review comment:
Agree with Gordon here. What about stating the problem this solves,
instead? Or, briefly mentioning why state is such an issue in this kind of
applications.
##########
File path: docs/index.md
##########
@@ -23,16 +23,16 @@ specific language governing permissions and limitations
under the License.
-->
-**Stateful Functions** is an open source framework that reduces the complexity
of building and orchestrating distributed stateful applications at scale.
-It brings together the benefits of stream processing with Apache Flink® and
Function-as-a-Service (FaaS) to provide a powerful abstraction for the next
generation of event-driven architectures.
+**Stateful Functions** is a framework, developed under the umbrella of Apache
Flink, that makes it simple to build **consistent stateful serverless
applications**.
Review comment:
Also, I wouldn't break the main sentence; the Flink part could be
attached at the end, so you get an uninterrupted definition of what StateFun is.
"Stateful Functions is a framework that makes it simple to build consistent
stateful serverless applications, developed under the umbrella of Apache Flink."
----------------------------------------------------------------
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
