Liferay 7 Major changes

 Here are some key changes of interest to existing Liferay developers:

  1. many out of the box portlets, features, and associated APIs have been extracted as OSGi modules

  2. Adoption of modern OSGi standards its modernized standards, such as Declarative Services, have made learning and using it much easier.

  3. Core Public APIs are provided through portal-kernel (previously known as portal-service); all other public APIs are provided by their own modules.

  4. You can reuse modules and libraries, and manage the dependencies among them.

  5. Registration of classes implementing extension points is now simpler and more consistent; it’s based on the standard @Component annotation instead of declarations in portal.properties or portlet.xml. 

  6. Complete integration of Liferay specific tools (such as Service Builder) within Maven and Gradle. Additionally we’ve adopted some new tools such as Bnd.


There are a lot of benefits of using OSGi and below are some:

  1. Easier to manage dependencies across module or plugin level
  2. Modules can be installed and uninstalled during the running server with no need to bounce the server
  3. Module versioning will help developers to reduce/stop class conflict for individual version of modules
  4. Deployment would be quite easy once you understand the build and deployment process through the blade tool
  5. Service contracts are loosely coupled. This means that services can be publish and consume from the service registry.
  6. It’s very fast due to being small and secure with small package/bundles.
  7. One more interesting thing here is, during development you don’t need to be dependent on Liferay SDK until and unless your module or individual project follows Liferay’s OSGi standards.
  8. In-short, this new framework will provide very good flexibility to the developer for the development and will increase productivity

Comments

Post a Comment

Popular posts from this blog

Azure App Service for Liferay DXP Installations

 Azure App Service is generally not the optimal choice for hosting Liferay DXP (Digital Experience Platform) installations. Liferay DXP is a robust, enterprise-grade platform that requires specific configurations and resources that are better suited for a more flexible and customizable infrastructure. Here are some considerations: 1. **Resource Requirements**: Liferay DXP typically requires significant memory, CPU, and storage resources. Azure App Service, being a Platform-as-a-Service (PaaS) offering, might not provide the necessary resource flexibility and control needed for optimal performance of Liferay DXP. 2. **Custom Configuration**: Liferay DXP often needs custom configurations and tuning, which are easier to manage on Infrastructure-as-a-Service (IaaS) offerings like Azure Virtual Machines or Azure Kubernetes Service (AKS). These services provide greater control over the operating system, middleware, and application layers. 3. **Database Requirements**: Liferay DXP require...
Read more

What Azure Infrastructure is better for Liferay DXP

 When choosing between Azure Container Apps (ACA) and Azure Kubernetes Service (AKS) for Liferay DXP installations, it's important to consider the specific requirements and characteristics of your deployment. Here's a comparison to help you decide: ### Azure Container Apps (ACA) **Pros:** 1. **Simplicity**: ACA provides a serverless environment for deploying containerized applications. It abstracts away much of the underlying infrastructure management. 2. **Cost-Effective**: ACA can be more cost-effective for smaller applications or less complex deployments due to its pay-per-use pricing model. 3. **Ease of Use**: ACA is designed to be easy to use, with less complexity in setup and management compared to AKS. **Cons:** 1. **Limited Control and Flexibility**: ACA abstracts much of the infrastructure, which means you have less control over the configurations and fine-tuning of the environment. 2. **Scalability**: While ACA does support scaling, it may not handle very large or com...
Read more