PureEngage On-Premises

Hi all,

we're using for a long while now the PSDK to get StatServer stats to display it in our own web tools.
As the StatServer is sending all stats to the client, which registered the stats, we have a single point of failure.

If this client application now crashes, we have an issue. Is there any good example of making a HA StatServer client or a active/active statserver client possible?

Regards

Christian

#ArchitectureandDesign
#Integrations
#Reporting/Analytics

------------------------------
Christian Rosenberger
Technical Lead Contact Center
Swisscom (Schweiz) AG
------------------------------

Added a little architecture diagram:


------------------------------
Christian Rosenberger
Swisscom (Schweiz) AG
------------------------------

Its not perfect, but we basically had our webserver make the same stat requests to two independent Stat Servers, so both Stat Servers are actively calculating the stats. 

Thus if we lose a Stat Server, the web server would just use the alternate Stat Server.  Or if the webserver goes down, the Stat Servers should continue calculating the stats.  And as long as an "alternate" webserver requests the same stats, it should continue where the original left off.  

At some point I'll play around with alternatives solutions.

------------------------------
Tony Morrow
------------------------------