Infrastructure Architecture and Deployment Options

Infrastructure architecture

The suggested infrastructure architecture for Digital Journey is comprised of five "stages":

  • Local environment - either a stand alone instance of the solution or a shared databases cloud instance

  • Remote development environment - similar to local, used to ensure application successfully deploys in a cloud environment

  • Systems integration environment - should be used to test integrations with third parties, either live or mocked

  • Pre-production/User acceptance environment - very similar to a live production environment, may have a reduced number of instances but should be at least High Availability capable, should be used for performance tests

  • Production - the final stage

In general teams produce, test and validate new developments in a local or shared setup. This development should then follow industry standard practices for Peer Reviewing and Continuous Integration (CI) and Continuous Delivery (CD) to the following stages up to the Production environment.

Recommended Architecture

In a productive environment we highly recommend redundancy of the application layer (with a minimum of 2 esign server and portal instances). On top of the application layer, a load-balancer should exist to distribute the load between the various instances.
All instances are served by a relational database, for which advise redundancy with a fail-over strategy.

diagram