Content Delivery

Yanel does not set any restrictions on the number of content "nodes" one can handle, but this is rather an issue of the actual content repository implementation (persistence manager) one chooses. The important thing is that Yanel allows one to choose any kind of persistence manager either by accessing it directly from within a resource or by using one or more content repository APIs (for example JCR or Yarep).

The implementation of the content navigation is also configurable per realm and therefore does not impose any restrictions.


The scalability of the number of concurrent sessions is of course related to performance in general, but since Yanel is clusterable it also depends on the right choice of application server. There are many well-known Java based application servers, for example Tomcat, Jetty, JBoss, WebSphere or WebLogic. Since Yanel itself nicely separates the application from the data handling/storage, one can easily deploy Yanel on multiple "working" machines (second layer) behind a load-balancer (first layer), whereas the data storage could be on separate shared machines (third layer), which are, for example, mounted by the "working" machines and replicated by the persistance manager itself, whereas the repository journal would be shared by the working machines.

Your comments are much appreciated

Is the content of this page unclear or you think it could be improved? Please add a comment and we will try to improve it accordingly.