Key New Features of Liferay DXP: Modularity, Semantic Versioning, Microservices, and More

With the release of the DXP version, Liferay has undergone a paradigm shift in its core product. This version defines a roadmap to address future technology trends such as microservices, digital experience management, smarter and faster build management.

In this article we select several new Liferay DXP features and explore them in detail.

Modularity

This means each Liferay module (feature) is now independent and can be separated from the core installation. Previously Liferay was a single large monolithic application; now it consists of multiple JARs, allowing enterprises to pick only the components they need, avoiding unnecessary performance overhead.

Benefits: Cleaner installations, reduced performance overhead, easier management, faster deployment, and simpler maintenance.

Who Benefits Most: Deployments that use many Liferay modules extensively.

Semantic Versioning

Liferay now allows multiple versions of the same module to run simultaneously on a single instance. For example, you can run one version of the Wiki feature while another version is being updated, with both old and new versions co‑existing.

Benefits: Users can access newer beta features without affecting existing functionality, and it enables A/B testing within the same instance.

Who Benefits Most: Scenarios that require frequent feature releases and where user acceptance is critical.

From Monolith to Microservices

Liferay is moving toward a microservice architecture. The application is divided into separate OSGi bundles, changing how portlets communicate—from IPC to service‑based interactions. Each portlet now behaves like a microservice, making attributes easily exposed and reusable across portlets.

Microservices let you split your product into smaller modules that can be upgraded at different speeds—for example, an e‑commerce cart may need bi‑weekly updates while a forum changes only yearly, making Liferay DXP an ideal platform.

Benefits: Fewer lines of code, better performance, faster deployment and maintenance.

Who Benefits Most: Large, multi‑tenant deployments where rapid feature rollout is a key success factor.

Public and Accessible Services

DXP enables the creation of smaller, more manageable modules and the export of services for external use. Services are reusable throughout the installation while remaining hidden from direct code access, improving system safety.

Benefits: Service isolation ensures that a failure in one service does not cascade, allowing production and consumption of services independently.

Who Benefits Most: Large‑scale deployments and DevOps environments where fault isolation and resilience are essential.

Faster Page Refresh

Liferay DXP uses the cutting‑edge Senna.js single‑page application (SPA) engine to dramatically improve site performance. The SPA loads all navigation resources on the first page load; subsequent interactions dynamically load content, eliminating full page reloads and leveraging HTML5 performance capabilities.

Benefits: A smoother user experience with near‑instant content refresh, enabling rich, fast‑running applications.

Who Benefits Most: All users—anyone appreciates a rapid browsing experience.

Extending EXT and Hook

DXP now provides OSGi package/module and service abstractions. Previously, core Liferay classes could only be overridden via EXT or hooks; now everything is a package that can be overridden directly, speeding up customization.

Benefits: Easier system maintenance and extension, automatic redirects, and simplified action handling without extra code.

Who Benefits Most: Developers and cross‑functional implementation teams, saving development time and avoiding redirect errors.

Broader Tool Support

Liferay now supports a variety of build tools—BND, Gradle, Maven, Gulp, Blade CLI, and Liferay Developer Studio—allowing organizations and developers to choose the tool that best fits their workflow.

Benefits: Opens Liferay to a larger community of developers proficient with different build systems.

Who Benefits Most: Developers and implementation teams who can select and use their preferred build tools.

Non‑Liferay Java Applications Can Access Pure Business Components

If you have a core Java library with business logic, Liferay now lets you reuse that logic without rewriting it for the platform.

Benefits: Code reuse saves time and cost, eliminating the need to refactor existing logic into Liferay.

Who Benefits Most: Teams with extensive custom business code looking to integrate it efficiently.

Cross‑System Reusable Classes

You can export services used by other system modules without requiring those modules to know the implementation details. Consumer modules import and use these services, acting as producers and multiple consumers.

Benefits: Build once, use everywhere.

For further details and community resources, see the original article link and the author’s various social and professional channels.