Caching Server for Distributed Locations
Using a caching server for the application server improves performance in distributed environments with multiple locations and high network latencies, especially in internationally distributed installations.
The AppServer Cache is the recommended caching solution for modern enterprise installations. It is designed to speed up content access and replaces earlier architectures based on Squid or Nginx caches, which no longer meet the recommended operating models under today’s HTTPS and SSL requirements.
The AppServer
Cache (service and program file pappcache.exe ) is a specialized
HTTP(S) cache and reverse proxy server for the
PARTsolutions ecosystem.
The local cache prevents unnecessary network round trips, especially with slow or distant connections. In particular, Catalog data that has already been loaded can be used locally, which significantly speeds up startup times and access to catalog data. In addition, cache contents are automatically updated or invalidated when changes are made to the catalog.
The caching server can be operated as an intermediary server between clients and the central application server. It stores frequently accessed data locally, thereby reducing the number of requests made over WAN connections.
Caching Server for Distributed Locations
Using a caching server for the application server improves performance in distributed environments with multiple locations and high network latencies, especially in internationally distributed installations.
The AppServer Cache is the recommended caching solution for modern enterprise installations. It is designed to speed up content access and replaces earlier architectures based on Squid or Nginx caches, which, given today’s HTTPS and SSL requirements, no longer comply with the recommended operating models.
The AppServer
Cache (service and program file pappcache.exe ) is a specialized
HTTP(S) cache and reverse proxy server for the
PARTsolutions ecosystem.
The local cache helps avoid unnecessary network round trips, especially with slow or distant connections. Catalog data that has already been loaded can be used locally, which significantly speeds up startup times and access to catalog data. In addition, cache contents are automatically updated or invalidated when catalog changes occur.
The caching server can be operated as an intermediate server between clients and the central application server. It stores frequently accessed data locally, thereby reducing the number of requests made over WAN connections.
The implemented functions include:
SSL/TLS termination with automatic certificate management via the Windows certificate store
Automatic reception of cache deletion and change notifications from the central AppServer
Support for WebSocket tunneling (e.g., for license and MZCOM services)
Automatic Copy the configuration from the
pappcache.cfgfileAutomatic reconfiguration when changes are made to the configuration file