Introducing Liferay Portal's architecture and framework
Liferay Portal's architecture supports high availability for mission-critical applications using clustering and the fully distributed cache and replication support across multiple servers. The following diagram has been taken from the Liferay forum written by Jorge Ferrer. This diagram depicts the various architectural layers and functionalities of portlets:
Figure 1.1: The Liferay architecture
Note
The preceding image was taken from https://www.liferay.com/web/jorge.ferrer/blog/-/blogs/liferay-s-architecture-the-beginning-of-a-blog-series site blog.
The Liferay Portal architecture is designed in such a way that it provides tons of features at one place:
- Frontend layer: This layer is the end user's interface
- Service layer: This contains the great majority of the business logic for the portal platform and all of the portlets included out of the box
- Persistence layer: Liferay relies on Hibernate to do most of its database access
- Web services API layer: This handles web services, such as JSON and SOAP
In Liferay, the service layer, persistence layer, and web services API layer are built automatically by that wonderful tool called Service Builder.
Note
Service Builder is the tool that glues together all of Liferay's layers and that hides the complexities of using Spring or Hibernate under the hood.
