Skip to content

Commit

Permalink
docs
Browse files Browse the repository at this point in the history
  • Loading branch information
Donald Oakes committed Feb 25, 2020
1 parent 66b9e91 commit 8560074
Showing 1 changed file with 3 additions and 4 deletions.
7 changes: 3 additions & 4 deletions docs/_docs/help/assetPersistence.html
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,9 @@
<body>
<h1>Asset Persistence</h1>

In MDW, the process definitions and other design-time resources <a href="assets.html">assets</a> are saved in a version control repository (GitHub) and
the runtime data is stored in a MySQL, Oracle or MongoDB database. This persistence model has the key advantage for delivering flexible, powerful branching and merging capabilities.
This is especially important to ensure the integrity of in-flight processes when multiple versions of an MDW workflow coexist in a production environment. The VCS Assets option
also offers dramatically improved performance in MDW Studio project access, as well as reduced server startup times.
MDW runtime data is stored in a MySQL, Oracle or MongoDB database, while process definitions and other design-time <a href="assets.html">assets</a>
are saved in a version control repository (Git). This asset persistence approach makes for powerful branching and merging capabilities.
This is especially important to ensure the integrity of in-flight processes when multiple versions of an MDW workflow coexist in a production environment.
<br/>
<h3>Motivation</h3>
As more and more of an application's business value moves into workflow, it's imperative that users have the tools to:
Expand Down

0 comments on commit 8560074

Please sign in to comment.