domhanak commented on code in PR #604:
URL:
https://github.com/apache/incubator-kie-kogito-docs/pull/604#discussion_r1537800962
##########
serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/getting-started/create-your-first-workflow-project.adoc:
##########
@@ -0,0 +1,184 @@
+= Creating a Quarkus Workflow Project
+
+As a developer, you can use {product_name} to create an application and in
this guide we want to explore different options and provide an overview of
available tools that can help in that purpose.
+
+We will also use Quarkus dev mode for iterative development and testing.
+
+As a common application development, we have different phases: Analysis,
Development and Deployment. Let's explore in detail each phase and what
{product_name} provides in each case:
+
+* <<proc-analysis-phase,Analysis and taking decisions phase>>
+** <<proc-adding-persistence,Adding persistence?>>
+** <<proc-adding-eventing,Adding eventing?>>
+** <<proc-adding-data-index-service,Adding Data Index service?>>
+** <<proc-adding-job-service,Adding Job service?>>
+
+* <<proc-development-phase,Development phase>>
+** <<proc-boostrapping-the-project,Bootstrapping a project, Creating a
workflow, Running your workflow application and Testing your workflow
application >>
+** <<proc-logging-configuration,How to configure logging>>
+** <<proc-dev-ui, Refine your workflow testing with Dev-UI>>
+* <<proc-deployment-phase,Deployment phase>>
+
+
+.Prerequisites
+* Java {java_min_version} is installed with `JAVA_HOME` configured
appropriately.
+* Apache Maven {maven_min_version} is installed.
+* {quarkus_cli_url}[Quarkus CLI] or
xref:testing-and-troubleshooting/kn-plugin-workflow-overview.adoc[Knative
Workflow CLI] {kn_cli_version} is installed.
+* Visual Studio Code with
https://marketplace.visualstudio.com/items?itemName=redhat.java[Red Hat Java
Extension]
+and
https://marketplace.visualstudio.com/items?itemName=redhat.vscode-extension-serverless-workflow-editor[Red
Hat Serverless Workflow Editor] is installed to edit your workflows.
+
+For more information about the tooling and the required dependencies, see
xref:getting-started/getting-familiar-with-our-tooling.adoc[Getting familiar
with {product_name} tooling].
+
+ifeval::["{kogito_version_redhat}" != ""]
+include::../../pages/_common-content/downstream-project-setup-instructions.adoc[]
+endif::[]
+
+
+[[proc-analysis-phase]]
+== Analysis and taking decisions phase
+
+In this phase the goal is to make some decisions about persistence, eventing,
security,.. What needs to be the topology of our application and how the
different components need to interact.
Review Comment:
```suggestion
Start by analyzing the requirements for your {product_name} application.
This will enable you to make decisions about persistence, eventing, security,
topology and component interaction needs of your application.
```
Maybe we do eventing -> event orchestration? Not sure what is better.
##########
serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/getting-started/create-your-first-workflow-project.adoc:
##########
@@ -0,0 +1,184 @@
+= Creating a Quarkus Workflow Project
+
+As a developer, you can use {product_name} to create an application and in
this guide we want to explore different options and provide an overview of
available tools that can help in that purpose.
+
+We will also use Quarkus dev mode for iterative development and testing.
+
+As a common application development, we have different phases: Analysis,
Development and Deployment. Let's explore in detail each phase and what
{product_name} provides in each case:
+
+* <<proc-analysis-phase,Analysis and taking decisions phase>>
+** <<proc-adding-persistence,Adding persistence?>>
+** <<proc-adding-eventing,Adding eventing?>>
+** <<proc-adding-data-index-service,Adding Data Index service?>>
+** <<proc-adding-job-service,Adding Job service?>>
+
+* <<proc-development-phase,Development phase>>
+** <<proc-boostrapping-the-project,Bootstrapping a project, Creating a
workflow, Running your workflow application and Testing your workflow
application >>
+** <<proc-logging-configuration,How to configure logging>>
+** <<proc-dev-ui, Refine your workflow testing with Dev-UI>>
+* <<proc-deployment-phase,Deployment phase>>
+
+
+.Prerequisites
+* Java {java_min_version} is installed with `JAVA_HOME` configured
appropriately.
+* Apache Maven {maven_min_version} is installed.
+* {quarkus_cli_url}[Quarkus CLI] or
xref:testing-and-troubleshooting/kn-plugin-workflow-overview.adoc[Knative
Workflow CLI] {kn_cli_version} is installed.
+* Visual Studio Code with
https://marketplace.visualstudio.com/items?itemName=redhat.java[Red Hat Java
Extension]
+and
https://marketplace.visualstudio.com/items?itemName=redhat.vscode-extension-serverless-workflow-editor[Red
Hat Serverless Workflow Editor] is installed to edit your workflows.
Review Comment:
```suggestion
* You have setup your environment according to the
xref:getting-started/preparing-environment.html#proc-advanced-local-environment-setup[advanced
environment setup] guide.
```
##########
serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/getting-started/create-your-first-workflow-project.adoc:
##########
@@ -0,0 +1,184 @@
+= Creating a Quarkus Workflow Project
+
+As a developer, you can use {product_name} to create an application and in
this guide we want to explore different options and provide an overview of
available tools that can help in that purpose.
+
+We will also use Quarkus dev mode for iterative development and testing.
+
+As a common application development, we have different phases: Analysis,
Development and Deployment. Let's explore in detail each phase and what
{product_name} provides in each case:
+
+* <<proc-analysis-phase,Analysis and taking decisions phase>>
+** <<proc-adding-persistence,Adding persistence?>>
+** <<proc-adding-eventing,Adding eventing?>>
+** <<proc-adding-data-index-service,Adding Data Index service?>>
+** <<proc-adding-job-service,Adding Job service?>>
+
+* <<proc-development-phase,Development phase>>
+** <<proc-boostrapping-the-project,Bootstrapping a project, Creating a
workflow, Running your workflow application and Testing your workflow
application >>
+** <<proc-logging-configuration,How to configure logging>>
+** <<proc-dev-ui, Refine your workflow testing with Dev-UI>>
+* <<proc-deployment-phase,Deployment phase>>
+
+
+.Prerequisites
+* Java {java_min_version} is installed with `JAVA_HOME` configured
appropriately.
+* Apache Maven {maven_min_version} is installed.
+* {quarkus_cli_url}[Quarkus CLI] or
xref:testing-and-troubleshooting/kn-plugin-workflow-overview.adoc[Knative
Workflow CLI] {kn_cli_version} is installed.
+* Visual Studio Code with
https://marketplace.visualstudio.com/items?itemName=redhat.java[Red Hat Java
Extension]
+and
https://marketplace.visualstudio.com/items?itemName=redhat.vscode-extension-serverless-workflow-editor[Red
Hat Serverless Workflow Editor] is installed to edit your workflows.
+
+For more information about the tooling and the required dependencies, see
xref:getting-started/getting-familiar-with-our-tooling.adoc[Getting familiar
with {product_name} tooling].
+
+ifeval::["{kogito_version_redhat}" != ""]
+include::../../pages/_common-content/downstream-project-setup-instructions.adoc[]
+endif::[]
+
+
+[[proc-analysis-phase]]
+== Analysis and taking decisions phase
Review Comment:
```suggestion
== Analysis phase
```
##########
serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/getting-started/create-your-first-workflow-project.adoc:
##########
@@ -0,0 +1,184 @@
+= Creating a Quarkus Workflow Project
+
+As a developer, you can use {product_name} to create an application and in
this guide we want to explore different options and provide an overview of
available tools that can help in that purpose.
+
+We will also use Quarkus dev mode for iterative development and testing.
+
+As a common application development, we have different phases: Analysis,
Development and Deployment. Let's explore in detail each phase and what
{product_name} provides in each case:
+
+* <<proc-analysis-phase,Analysis and taking decisions phase>>
+** <<proc-adding-persistence,Adding persistence?>>
+** <<proc-adding-eventing,Adding eventing?>>
+** <<proc-adding-data-index-service,Adding Data Index service?>>
+** <<proc-adding-job-service,Adding Job service?>>
+
+* <<proc-development-phase,Development phase>>
+** <<proc-boostrapping-the-project,Bootstrapping a project, Creating a
workflow, Running your workflow application and Testing your workflow
application >>
+** <<proc-logging-configuration,How to configure logging>>
+** <<proc-dev-ui, Refine your workflow testing with Dev-UI>>
+* <<proc-deployment-phase,Deployment phase>>
+
+
+.Prerequisites
+* Java {java_min_version} is installed with `JAVA_HOME` configured
appropriately.
+* Apache Maven {maven_min_version} is installed.
+* {quarkus_cli_url}[Quarkus CLI] or
xref:testing-and-troubleshooting/kn-plugin-workflow-overview.adoc[Knative
Workflow CLI] {kn_cli_version} is installed.
+* Visual Studio Code with
https://marketplace.visualstudio.com/items?itemName=redhat.java[Red Hat Java
Extension]
+and
https://marketplace.visualstudio.com/items?itemName=redhat.vscode-extension-serverless-workflow-editor[Red
Hat Serverless Workflow Editor] is installed to edit your workflows.
+
+For more information about the tooling and the required dependencies, see
xref:getting-started/getting-familiar-with-our-tooling.adoc[Getting familiar
with {product_name} tooling].
+
+ifeval::["{kogito_version_redhat}" != ""]
+include::../../pages/_common-content/downstream-project-setup-instructions.adoc[]
+endif::[]
+
+
+[[proc-analysis-phase]]
+== Analysis and taking decisions phase
+
+In this phase the goal is to make some decisions about persistence, eventing,
security,.. What needs to be the topology of our application and how the
different components need to interact.
+
+[[proc-adding-persistence]]
+=== Adding persistence?
+
+We need to decide if we need to ensure that your workflow instances remain
consistent in the context.
+When the persistence is not configured, an in-memory persistence is used,
making all the {workflow_instance} information volatile upon runtime restarts.
In this case if the workflow runtime is restarted.
+
+At this stage we need to decide what kind of persistence is needed and
configure it properly.
+You can find deeper explained it in {product_name} persistence
xref:use-cases/advanced-developer-use-cases/persistence/persistence-core-concepts.adoc[]
+
+You can find more information about how to create an application which writes
to and reads from a database at Quarkus guide
link:https://quarkus.io/guides/getting-started-dev-services[Your second Quarkus
application]
Review Comment:
```suggestion
If your application requires persistence, you need to decide what kind of
persistence is needed and configure it properly.
Follow the {product_name}
xref:use-cases/advanced-developer-use-cases/persistence/persistence-core-concepts.adoc[persistence
guide] for more information.
You can find more information about how to create an application which
writes to and reads from a database following
link:https://quarkus.io/guides/getting-started-dev-services[Your second Quarkus
application] guide.
```
##########
serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/getting-started/create-your-first-workflow-project.adoc:
##########
@@ -0,0 +1,184 @@
+= Creating a Quarkus Workflow Project
+
+As a developer, you can use {product_name} to create an application and in
this guide we want to explore different options and provide an overview of
available tools that can help in that purpose.
+
+We will also use Quarkus dev mode for iterative development and testing.
+
+As a common application development, we have different phases: Analysis,
Development and Deployment. Let's explore in detail each phase and what
{product_name} provides in each case:
+
+* <<proc-analysis-phase,Analysis and taking decisions phase>>
+** <<proc-adding-persistence,Adding persistence?>>
+** <<proc-adding-eventing,Adding eventing?>>
+** <<proc-adding-data-index-service,Adding Data Index service?>>
+** <<proc-adding-job-service,Adding Job service?>>
+
+* <<proc-development-phase,Development phase>>
+** <<proc-boostrapping-the-project,Bootstrapping a project, Creating a
workflow, Running your workflow application and Testing your workflow
application >>
+** <<proc-logging-configuration,How to configure logging>>
+** <<proc-dev-ui, Refine your workflow testing with Dev-UI>>
+* <<proc-deployment-phase,Deployment phase>>
+
+
+.Prerequisites
+* Java {java_min_version} is installed with `JAVA_HOME` configured
appropriately.
+* Apache Maven {maven_min_version} is installed.
+* {quarkus_cli_url}[Quarkus CLI] or
xref:testing-and-troubleshooting/kn-plugin-workflow-overview.adoc[Knative
Workflow CLI] {kn_cli_version} is installed.
+* Visual Studio Code with
https://marketplace.visualstudio.com/items?itemName=redhat.java[Red Hat Java
Extension]
+and
https://marketplace.visualstudio.com/items?itemName=redhat.vscode-extension-serverless-workflow-editor[Red
Hat Serverless Workflow Editor] is installed to edit your workflows.
+
+For more information about the tooling and the required dependencies, see
xref:getting-started/getting-familiar-with-our-tooling.adoc[Getting familiar
with {product_name} tooling].
+
+ifeval::["{kogito_version_redhat}" != ""]
+include::../../pages/_common-content/downstream-project-setup-instructions.adoc[]
+endif::[]
+
+
+[[proc-analysis-phase]]
+== Analysis and taking decisions phase
+
+In this phase the goal is to make some decisions about persistence, eventing,
security,.. What needs to be the topology of our application and how the
different components need to interact.
+
+[[proc-adding-persistence]]
+=== Adding persistence?
+
+We need to decide if we need to ensure that your workflow instances remain
consistent in the context.
+When the persistence is not configured, an in-memory persistence is used,
making all the {workflow_instance} information volatile upon runtime restarts.
In this case if the workflow runtime is restarted.
Review Comment:
```suggestion
{product_name} applications use an in-memory persistence by default. This
makes all the {workflow_instance} information volatile upon runtime restarts.
In case of this guide, when the workflow runtime is restarted.
As a developer, you need to decide if there is a need to ensure that your
workflow instances remain consistent in the context.
```
##########
serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/getting-started/create-your-first-workflow-project.adoc:
##########
@@ -0,0 +1,184 @@
+= Creating a Quarkus Workflow Project
+
+As a developer, you can use {product_name} to create an application and in
this guide we want to explore different options and provide an overview of
available tools that can help in that purpose.
+
+We will also use Quarkus dev mode for iterative development and testing.
+
+As a common application development, we have different phases: Analysis,
Development and Deployment. Let's explore in detail each phase and what
{product_name} provides in each case:
+
+* <<proc-analysis-phase,Analysis and taking decisions phase>>
+** <<proc-adding-persistence,Adding persistence?>>
+** <<proc-adding-eventing,Adding eventing?>>
+** <<proc-adding-data-index-service,Adding Data Index service?>>
+** <<proc-adding-job-service,Adding Job service?>>
+
+* <<proc-development-phase,Development phase>>
+** <<proc-boostrapping-the-project,Bootstrapping a project, Creating a
workflow, Running your workflow application and Testing your workflow
application >>
+** <<proc-logging-configuration,How to configure logging>>
+** <<proc-dev-ui, Refine your workflow testing with Dev-UI>>
+* <<proc-deployment-phase,Deployment phase>>
+
+
+.Prerequisites
+* Java {java_min_version} is installed with `JAVA_HOME` configured
appropriately.
+* Apache Maven {maven_min_version} is installed.
+* {quarkus_cli_url}[Quarkus CLI] or
xref:testing-and-troubleshooting/kn-plugin-workflow-overview.adoc[Knative
Workflow CLI] {kn_cli_version} is installed.
+* Visual Studio Code with
https://marketplace.visualstudio.com/items?itemName=redhat.java[Red Hat Java
Extension]
+and
https://marketplace.visualstudio.com/items?itemName=redhat.vscode-extension-serverless-workflow-editor[Red
Hat Serverless Workflow Editor] is installed to edit your workflows.
+
+For more information about the tooling and the required dependencies, see
xref:getting-started/getting-familiar-with-our-tooling.adoc[Getting familiar
with {product_name} tooling].
+
+ifeval::["{kogito_version_redhat}" != ""]
+include::../../pages/_common-content/downstream-project-setup-instructions.adoc[]
+endif::[]
+
+
+[[proc-analysis-phase]]
+== Analysis and taking decisions phase
+
+In this phase the goal is to make some decisions about persistence, eventing,
security,.. What needs to be the topology of our application and how the
different components need to interact.
+
+[[proc-adding-persistence]]
+=== Adding persistence?
+
+We need to decide if we need to ensure that your workflow instances remain
consistent in the context.
+When the persistence is not configured, an in-memory persistence is used,
making all the {workflow_instance} information volatile upon runtime restarts.
In this case if the workflow runtime is restarted.
+
+At this stage we need to decide what kind of persistence is needed and
configure it properly.
+You can find deeper explained it in {product_name} persistence
xref:use-cases/advanced-developer-use-cases/persistence/persistence-core-concepts.adoc[]
+
+You can find more information about how to create an application which writes
to and reads from a database at Quarkus guide
link:https://quarkus.io/guides/getting-started-dev-services[Your second Quarkus
application]
+[[proc-adding-eventing]]
+=== Adding eventing?
+
+Quarkus unifies reactive and imperative programming you can find it more
explained in the Quarkus guide
link:https://quarkus.io/guides/quarkus-reactive-architecture[Quarkus Reactive
Architecture]
+
+In this phase we need to decide how the Event-Driven Architecture needs to be
added to our project. We have different options here:
Review Comment:
Could we please add some case about why I want eventing etc. Something
similar to persistence section.
##########
serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/getting-started/create-your-first-workflow-project.adoc:
##########
@@ -0,0 +1,184 @@
+= Creating a Quarkus Workflow Project
+
+As a developer, you can use {product_name} to create an application and in
this guide we want to explore different options and provide an overview of
available tools that can help in that purpose.
+
+We will also use Quarkus dev mode for iterative development and testing.
+
+As a common application development, we have different phases: Analysis,
Development and Deployment. Let's explore in detail each phase and what
{product_name} provides in each case:
+
+* <<proc-analysis-phase,Analysis and taking decisions phase>>
+** <<proc-adding-persistence,Adding persistence?>>
+** <<proc-adding-eventing,Adding eventing?>>
+** <<proc-adding-data-index-service,Adding Data Index service?>>
+** <<proc-adding-job-service,Adding Job service?>>
+
+* <<proc-development-phase,Development phase>>
+** <<proc-boostrapping-the-project,Bootstrapping a project, Creating a
workflow, Running your workflow application and Testing your workflow
application >>
+** <<proc-logging-configuration,How to configure logging>>
+** <<proc-dev-ui, Refine your workflow testing with Dev-UI>>
+* <<proc-deployment-phase,Deployment phase>>
+
+
+.Prerequisites
+* Java {java_min_version} is installed with `JAVA_HOME` configured
appropriately.
+* Apache Maven {maven_min_version} is installed.
+* {quarkus_cli_url}[Quarkus CLI] or
xref:testing-and-troubleshooting/kn-plugin-workflow-overview.adoc[Knative
Workflow CLI] {kn_cli_version} is installed.
+* Visual Studio Code with
https://marketplace.visualstudio.com/items?itemName=redhat.java[Red Hat Java
Extension]
+and
https://marketplace.visualstudio.com/items?itemName=redhat.vscode-extension-serverless-workflow-editor[Red
Hat Serverless Workflow Editor] is installed to edit your workflows.
+
+For more information about the tooling and the required dependencies, see
xref:getting-started/getting-familiar-with-our-tooling.adoc[Getting familiar
with {product_name} tooling].
+
+ifeval::["{kogito_version_redhat}" != ""]
+include::../../pages/_common-content/downstream-project-setup-instructions.adoc[]
+endif::[]
+
+
+[[proc-analysis-phase]]
+== Analysis and taking decisions phase
+
+In this phase the goal is to make some decisions about persistence, eventing,
security,.. What needs to be the topology of our application and how the
different components need to interact.
+
+[[proc-adding-persistence]]
+=== Adding persistence?
+
+We need to decide if we need to ensure that your workflow instances remain
consistent in the context.
+When the persistence is not configured, an in-memory persistence is used,
making all the {workflow_instance} information volatile upon runtime restarts.
In this case if the workflow runtime is restarted.
+
+At this stage we need to decide what kind of persistence is needed and
configure it properly.
+You can find deeper explained it in {product_name} persistence
xref:use-cases/advanced-developer-use-cases/persistence/persistence-core-concepts.adoc[]
+
+You can find more information about how to create an application which writes
to and reads from a database at Quarkus guide
link:https://quarkus.io/guides/getting-started-dev-services[Your second Quarkus
application]
+[[proc-adding-eventing]]
+=== Adding eventing?
+
+Quarkus unifies reactive and imperative programming you can find it more
explained in the Quarkus guide
link:https://quarkus.io/guides/quarkus-reactive-architecture[Quarkus Reactive
Architecture]
+
+In this phase we need to decide how the Event-Driven Architecture needs to be
added to our project. We have different options here:
+
+* *Kafka Connector* for Reactive Messaging.
xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-producing-events-with-kafka.adoc[]
+* *Knative* eventing.
xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc[]
Review Comment:
```suggestion
* *Kafka Connector* for Reactive Messaging. See
xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-producing-events-with-kafka.adoc[]
for more details.
* *Knative* eventing. See
xref:use-cases/advanced-developer-use-cases/event-orchestration/consume-produce-events-with-knative-eventing.adoc[]
for more details.
```
##########
serverlessworkflow/modules/ROOT/pages/use-cases/advanced-developer-use-cases/getting-started/create-your-first-workflow-project.adoc:
##########
@@ -0,0 +1,184 @@
+= Creating a Quarkus Workflow Project
+
+As a developer, you can use {product_name} to create an application and in
this guide we want to explore different options and provide an overview of
available tools that can help in that purpose.
+
+We will also use Quarkus dev mode for iterative development and testing.
+
+As a common application development, we have different phases: Analysis,
Development and Deployment. Let's explore in detail each phase and what
{product_name} provides in each case:
+
+* <<proc-analysis-phase,Analysis and taking decisions phase>>
+** <<proc-adding-persistence,Adding persistence?>>
+** <<proc-adding-eventing,Adding eventing?>>
+** <<proc-adding-data-index-service,Adding Data Index service?>>
+** <<proc-adding-job-service,Adding Job service?>>
+
+* <<proc-development-phase,Development phase>>
+** <<proc-boostrapping-the-project,Bootstrapping a project, Creating a
workflow, Running your workflow application and Testing your workflow
application >>
+** <<proc-logging-configuration,How to configure logging>>
+** <<proc-dev-ui, Refine your workflow testing with Dev-UI>>
+* <<proc-deployment-phase,Deployment phase>>
+
+
+.Prerequisites
+* Java {java_min_version} is installed with `JAVA_HOME` configured
appropriately.
+* Apache Maven {maven_min_version} is installed.
+* {quarkus_cli_url}[Quarkus CLI] or
xref:testing-and-troubleshooting/kn-plugin-workflow-overview.adoc[Knative
Workflow CLI] {kn_cli_version} is installed.
+* Visual Studio Code with
https://marketplace.visualstudio.com/items?itemName=redhat.java[Red Hat Java
Extension]
+and
https://marketplace.visualstudio.com/items?itemName=redhat.vscode-extension-serverless-workflow-editor[Red
Hat Serverless Workflow Editor] is installed to edit your workflows.
+
+For more information about the tooling and the required dependencies, see
xref:getting-started/getting-familiar-with-our-tooling.adoc[Getting familiar
with {product_name} tooling].
+
+ifeval::["{kogito_version_redhat}" != ""]
+include::../../pages/_common-content/downstream-project-setup-instructions.adoc[]
+endif::[]
+
+
+[[proc-analysis-phase]]
+== Analysis and taking decisions phase
+
+In this phase the goal is to make some decisions about persistence, eventing,
security,.. What needs to be the topology of our application and how the
different components need to interact.
+
+[[proc-adding-persistence]]
+=== Adding persistence?
+
+We need to decide if we need to ensure that your workflow instances remain
consistent in the context.
+When the persistence is not configured, an in-memory persistence is used,
making all the {workflow_instance} information volatile upon runtime restarts.
In this case if the workflow runtime is restarted.
+
+At this stage we need to decide what kind of persistence is needed and
configure it properly.
+You can find deeper explained it in {product_name} persistence
xref:use-cases/advanced-developer-use-cases/persistence/persistence-core-concepts.adoc[]
+
+You can find more information about how to create an application which writes
to and reads from a database at Quarkus guide
link:https://quarkus.io/guides/getting-started-dev-services[Your second Quarkus
application]
+[[proc-adding-eventing]]
+=== Adding eventing?
+
+Quarkus unifies reactive and imperative programming you can find it more
explained in the Quarkus guide
link:https://quarkus.io/guides/quarkus-reactive-architecture[Quarkus Reactive
Architecture]
Review Comment:
```suggestion
Quarkus unifies reactive and imperative programming you can find more
information about this in the
link:https://quarkus.io/guides/quarkus-reactive-architecture[Quarkus Reactive
Architecture] guide.
```
--
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]
