Performance

Load Balancing

Some architectures need to evolve in scalability and high availability (failover).

For these reasons, WEDIA WMS is able to be clustered in vertical and/or horizontal ways :
- vertical clustering : this is to put several WEDIA WMS instances on the same server, each with its JVM and sharing a common database and a file directory with the same resources. In this approach, there is no question of availability but just high scalability.

- horizontal clustering : it is to install multiple servers, each containing a JVM and one WEDIA WMS instance, and sharing a common database and a file directory with the same resources. This approach addresses both the high availability and scalability problem.

WEDIA WMS can be clustered in horizontal and vertical way in the same time. 

Page Caching

WEDIA WMS offers a cache management page (JSP template). This dynamic cache is designed to make static site (all or part).

This caching allows multiple combinations, to render as:
- A static page, for a given period (1 second, 1 hour, ...)
- A static page, which includes a dynamic page (for example : one e-commerce site with basket functionnality)
- A single static page to standard users and dynamic for premium.
- A single static page to a non authenticated user, full dynamic for authenticated user
- A cached page for multiple profiles, knowing that the content varies by profile

Advanced Caching

WEDIA WMS has an advanced caching feature. It is an integrated mechanism to cache used objects in memory. The cache engine reduces server and database exchanges. No specific development is needed.

Static Content Export

WEDIA WMS can publish contents to static HTML or XML pages. It is therefore possible to publish a static site (all or a part).