Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Joget DX runs on industry standard technologies, and can be deployed on a standard web application architecture either on-premise, on public/private cloud platforms (Amazon AWS, Microsoft Azure, Google Cloud Platform, etc), or on cloud-native hybrid cloud platforms (Kubernetes, Red Hat OpenShift,
 

Figure 1: Standard Infrastructure Architecture

  • Load Balancer or Reverse Proxy: Forwards external requests to the application servers, and performs load balancing if required.
  • Application Server: Java EE compliant application server, running on any Java-supported operating system.
  • Database Server: Main relational database (RDBMS) for platform and application data.
  • File Storage: Shared file storage for configuration and runtime files.

Note
IMPORTANT NOTE: The architecture presented above is only for reference, and may vary according to requirements and environment. The Joget DX platform itself is packaged as a Java WAR file that is deployed to one or more Java EE application servers.

...

Joget DX is highly open and flexible , and can be deployed in a large variety of environments. 

...

  • Apache HTTP Server 2.4 and above
  • NGINX 1.2 and above
  • Any hardware or software load balancer or reverse proxy that transparently forwards requests to the application server

Note

IMPORTANT NOTE: Please note that there is minimal configuration required in Joget DX itself and most of the configuration are on the separate infrastructure components, so it is vital to ensure that you have sufficient expertise in your chosen products. Alternatively, consider hosting at Joget Cloud to outsource the infrastructure management.

...

  1. Total number of users
  2. Maximum expected concurrent users
  3. Complexity of apps running on the platform
  4. Complexity of the processes running on the platform
  5. Amount of data generated
  6. Integrations points
  7. Network infrastructureInfrastructure

Every environment is different and the following are base guidelines for high-level reference only.

...

Note

RECOMMENDATIONS: 

  • To determine actual requirements, conduct performance tests on specific use cases and environments.
  • Start small and plan to scale.
  • For large-scale implementations, consider using using Kubernetes or Red Hat OpenShift, but ensure that you have sufficient expertise and support to manage the platform.

...

...

RECOMMENDATIONS: 

  • To determine actual requirements, conduct performance tests on specific use cases and environments.
  • Start small and plan to scale.
  • For large-scale implementations, consider using Kubernetes or Red Hat OpenShift, but ensure that you have sufficient expertise and support to manage the platform.

...