nmirasch commented on code in PR #555: URL: https://github.com/apache/incubator-kie-kogito-docs/pull/555#discussion_r1506318305
########## 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 remains 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 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. ``` ########## serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/persistence/postgresql-advanced-concepts.adoc: ########## @@ -0,0 +1,78 @@ += Postgresql Advanced Concepts +:compat-mode!: +// Metadata: +:description: Running Quarkus Workflow Application using PostgresSQL +:keywords: kogito, workflow, quarkus, serverless, quarkus-cli, persistence, postgresql +:flyway_url: https://flywaydb.org/ + +This document shows a detailed view of the database structure when you use the PostgreSQL persistence. + +.Prerequisites +* You are familiar with the xref:use-cases/advanced-developer-use-cases/persistence/persistence-core-concepts.adoc[Persistence Core concepts] guide +* You are familiar with the xref:use-cases/advanced-developer-use-cases/persistence/persistence-with-postgresql.adoc[Persistence with PostreSQL] guide + +As it was introduced in the xref:use-cases/advanced-developer-use-cases/persistence/persistence-core-concepts.adoc[Persistence Core concepts], every workflow instance requires some status information and data to execute, this information is automatically managed by the workflows runtime. And is persisted at different moments of the workflow execution in the form of a snapshot. Review Comment: ```suggestion As it was introduced in the xref:use-cases/advanced-developer-use-cases/persistence/persistence-core-concepts.adoc[Persistence Core concepts], 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 in the form of a snapshot. ``` ########## serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/persistence/postgresql-advanced-concepts.adoc: ########## @@ -0,0 +1,78 @@ += Postgresql Advanced Concepts +:compat-mode!: +// Metadata: +:description: Running Quarkus Workflow Application using PostgresSQL +:keywords: kogito, workflow, quarkus, serverless, quarkus-cli, persistence, postgresql +:flyway_url: https://flywaydb.org/ + +This document shows a detailed view of the database structure when you use the PostgreSQL persistence. + +.Prerequisites +* You are familiar with the xref:use-cases/advanced-developer-use-cases/persistence/persistence-core-concepts.adoc[Persistence Core concepts] guide +* You are familiar with the xref:use-cases/advanced-developer-use-cases/persistence/persistence-with-postgresql.adoc[Persistence with PostreSQL] guide + +As it was introduced in the xref:use-cases/advanced-developer-use-cases/persistence/persistence-core-concepts.adoc[Persistence Core concepts], every workflow instance requires some status information and data to execute, this information is automatically managed by the workflows runtime. And is persisted at different moments of the workflow execution in the form of a snapshot. + +In the following diagram you can see the tables that support these information: + +image::persistence/Persistence-PostgreSQL-Advanced.png[] + +[NOTE] +==== +Regular backup procedures are not performed by the workflows runtime persistence, and thus, they must be provided by the installation owner. +==== + +== `process_instances` +This table stores the workflows snapshots. These snapshots are stored in binary format, and by default, are maintained in the database as long as the workflow instance is active. When a workflow instance finalizes it execution, the corresponding snapshot is removed from the database for optimization purposes. Review Comment: ```suggestion This table stores the workflows snapshots. These snapshots are stored in binary format, and by default, are maintained in the database as long as the workflow instance is active. When a workflow instance finalizes its execution, the corresponding snapshot is removed from the database for optimization purposes. ``` ########## serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/persistence/postgresql-advanced-concepts.adoc: ########## @@ -0,0 +1,78 @@ += Postgresql Advanced Concepts +:compat-mode!: +// Metadata: +:description: Running Quarkus Workflow Application using PostgresSQL +:keywords: kogito, workflow, quarkus, serverless, quarkus-cli, persistence, postgresql +:flyway_url: https://flywaydb.org/ + +This document shows a detailed view of the database structure when you use the PostgreSQL persistence. + +.Prerequisites +* You are familiar with the xref:use-cases/advanced-developer-use-cases/persistence/persistence-core-concepts.adoc[Persistence Core concepts] guide +* You are familiar with the xref:use-cases/advanced-developer-use-cases/persistence/persistence-with-postgresql.adoc[Persistence with PostreSQL] guide + +As it was introduced in the xref:use-cases/advanced-developer-use-cases/persistence/persistence-core-concepts.adoc[Persistence Core concepts], every workflow instance requires some status information and data to execute, this information is automatically managed by the workflows runtime. And is persisted at different moments of the workflow execution in the form of a snapshot. + +In the following diagram you can see the tables that support these information: + +image::persistence/Persistence-PostgreSQL-Advanced.png[] + +[NOTE] +==== +Regular backup procedures are not performed by the workflows runtime persistence, and thus, they must be provided by the installation owner. Review Comment: ```suggestion Regular backup procedures are not performed by the workflow's runtime persistence, and thus, they must be provided by the installation owner. ``` ########## 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 remains 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 workflows 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 pause that instance execution. Review Comment: ```suggestion 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. ``` ########## 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 remains 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 workflows 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. ``` -- 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]
