Hi William

Here are some pointers:

• Do maintain the development and production Joget Workflow on separate servers.
• The development servers are usually:
  • Lowerspecs hardware.
  • Has a Joget license for a smaller number of users, compared to the production server.
  • Has multiple database engine in the server which you can switch to for testing.
  • Because it is a development server, you can add or delete all the database records, processes, apps etc. and start over again on a clean slate.
  • With sufficient hardware capacity (i.e. memory), you can install and run different versions of Joget Workflow (v5 & v6 on different ports and separate databases) and run them concurrently for version testing.
  • You can have the first development server for Joget Workflow on Linux/Ubuntu and a second development server for Windows OS (to maintain the same platform and OS as your clients production servers).
  • The development server is used to test new Joget Workflow builds or releases before deploying to the live server.
• The production servers are usually:
  • Higher specs hardware and connected to the internet for global access with SSL security.
  • Has a Joget license for unlimited users.
  • Has only a single database engine in the production server or Joget accesses the database in a separate db server for optimal performance.
  • Run only one copy of Joget Workflow for optimal memory usage and disk storage or could be a Joget Workflow Cluster version with a load balancer server.
  • The Joget Workflow app and process designs are minimally changed, meaning it has fewer version changes. Compared if in a development server which has many revisions of the process design, and each change of the process design is saved into the database. The less version records (both in app versions and process versions) in Joget Workflow, and consequently the smaller the database storing the app code, the faster the app will execute.

Further readings:

• Version Control
• Update Existing Running Process Instances to the Newer Process Flow After Process Changes
• Powerpoint Slides on Version Control
• Joget Workflow Clustering Guide