As service providers scale, they will need to process greater number of UDR records and larger numbers of user packages. In such a scenario it is desirable to have the web server, app server and database on separate Hyper-V Hosts. As long as processing power is adequate, the web server and app server can be placed on their own Hyper-V Host. It is strongly recommended that the Database server runs on it’s own physical box.
The distributed nature of EngageIP allows it to scale vertically and horizontally. More processing power can be added for enhanced performance. Furthermore, individual services can be deployed on their own virtual machines – as an example, the rating and billing services are particularly prone to resource contention (based on configuration complexity) and can be candidates for standalone deployments.
The typical software and hardware requirements for a basic to modest deployment are listed below. The exact specifications for a given customer will be based on their unique needs and uncovered during the design engagement process with their solutions consultant.
While this basic deployment scales well, it lacks redundancy. If the VM hosting the app server were to crash, the EngageIP system would go offline until the VM recovers. For additional redundancy, it is recommended to have multiple redundant app, web server and database instances.