Databases Reference
In-Depth Information
As shown in the preceding diagram, we have one Solr master server and one Solr
slave server. The Solr master server is configured such that it automatically replicates
indexes to the slave server. Each Liferay Portal application server will be connected
to both master and slave servers. The Liferay Solr web plugin provides a way to
configure separate Solr servers for read and write operations. To scale the search
functionality further, we can also configure separate slave servers for each Liferay
portal node. This will reduce the load on the slave server by limiting search requests.
Summary
We have covered most of the important architectural aspects that we should consider
while designing a Liferay-based portal. We learned about the reference architecture
of Liferay-Portal-based solutions and the sizing approach. We also learned about
various architectural options for managing the Document and Medial library,
caching, and static content delivery. We also talked about caching options available
to boost performance. In the last section, we learned various architectural options
available for the search functionality.
Now let's get ready to learn about load balancing and clustering in detail.
