ricardozanini commented on code in PR #555:
URL:
https://github.com/apache/incubator-kie-kogito-docs/pull/555#discussion_r1506402170
##########
serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/persistence/persistence-core-concepts.adoc:
##########
@@ -0,0 +1,44 @@
+= Core Concepts
+:compat-mode!:
+// Metadata:
+:description: Running Quarkus Workflow Application using PostgresSQL
+:keywords: kogito, workflow, quarkus, serverless, quarkus-cli, persistence,
postgresql
+
+The SonataFlow workflows runtime persistence is the mechanism to ensure that
your workflow instances remain consistent in the context of an error or a
runtime restart. For example, a pod restart, a programmed maintenance shutdown,
etc.
Review Comment:
```suggestion
The {product_name} workflow runtime persistence is the mechanism to ensure
that your workflow instances remain consistent in the context of an error or a
runtime restart. For example, a pod restart, a programmed maintenance shutdown,
etc.
```
##########
serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/persistence/persistence-core-concepts.adoc:
##########
@@ -0,0 +1,44 @@
+= Core Concepts
+:compat-mode!:
+// Metadata:
+:description: Running Quarkus Workflow Application using PostgresSQL
+:keywords: kogito, workflow, quarkus, serverless, quarkus-cli, persistence,
postgresql
+
+The SonataFlow workflows runtime persistence is the mechanism to ensure that
your workflow instances remain consistent in the context of an error or a
runtime restart. For example, a pod restart, a programmed maintenance shutdown,
etc.
+
+Every workflow instance requires some status information and data to execute,
this information is automatically managed by the workflow's runtime, and is
persisted at different moments of the workflow execution.
Review Comment:
```suggestion
Every workflow instance requires some status information and data to
execute, this information is automatically managed by the workflow's runtime
and is persisted at different moments of the workflow execution.
```
##########
serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/persistence/persistence-core-concepts.adoc:
##########
@@ -0,0 +1,44 @@
+= Core Concepts
+:compat-mode!:
+// Metadata:
+:description: Running Quarkus Workflow Application using PostgresSQL
+:keywords: kogito, workflow, quarkus, serverless, quarkus-cli, persistence,
postgresql
+
+The SonataFlow workflows runtime persistence is the mechanism to ensure that
your workflow instances remain consistent in the context of an error or a
runtime restart. For example, a pod restart, a programmed maintenance shutdown,
etc.
+
+Every workflow instance requires some status information and data to execute,
this information is automatically managed by the workflow's runtime, and is
persisted at different moments of the workflow execution.
+
+For example, when a workflow instance reaches a state that needs to wait for
an event, the engine takes a snapshot of the most relevant information, stores
it in the database, and pauses that instance execution.
+In this way, resources like memory are released, and can be used by other
executing instances.
Review Comment:
```suggestion
In this way, resources like memory are released and can be used by other
executing instances.
```
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
