Your browser (Internet Explorer 7 or lower) is out of date. It has known security flaws and may not display all features of this and other websites. Learn how to update your browser.

X

Navigate / search

Liferay Terracotta Configuration

Caching is one of the most important technique to improve performance of any solution. By default Liferay portal implements caching using EHCache framework. When we implement clustered deployment of Liferay portal solution, we need to make sure we synchronize caches across all the nodes. Cache synchronization is a very common issue to deal with any scalable solution. Essentially there are two types of options to solve the issue.

  1. Using Cache Replication
  2. Using Distributed Cache

EHCache provides different way of implementing cache replication. Also Liferay supports cache replication using Cluster Link. But if we need highly scalable solution where in we are planning to keep lot of data in cache then distributed cache is better option. In distributed cache individual node keeps only required data in cache. Centralized cache server keeps consolidated cache of all the nodes. Terracotta provides EHCache based distributed cache. In this blog I will provide how to configure Liferay to use Terracotta based distributed cache instead of EHCache based replicated cache.

Read more

Database Sharding with Liferay – Part 1

Liferay portal allows hosting completely unrelated portals using a feature called Portal Instances. Using Liferay control panel we can create multiple portal instances. Each portal instance will have its own users, sites, organizations, user groups and so on. Internally portal instance is also referred as company. Liferay keeps company id in almost all tables to distinguish data based on portal instance. If many portal instances are created and each portal instance has huge amount of data then at certain point performance of database will deteriorate because of huge amount of data. In this situation it will be a good idea to partition the data based on instance id or company id. This technique to distribute rows of table in multiple databases is called Database Sharding. Liferay portal supports this feature. This blog will explain how to use Database Sharding feature with Liferay 6.1.

Read more

Liferay 6.1 Performance: serving static resources through Apache Web server

It is known fact that if we serve static resources like images, java script, css etc. through web server then we can improve response time. This fact also applies to Liferay portal as well. By default static resources of Portal, Portlet and Themes are served through Liferay portal server. Liferay portal adds certain overhead like servlet filters to serve these static resources. If we serve these static resources directly from web server then we can improve the response time. In majority of the production deployments web server is used in front of Liferay portal servers. This blog provides step by step guide to configure Apache Web server to serve static resource.