Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Behaviour of the Liferay Infrastructure on Liferay PaaS when a Headless API is called during deployment

Written By

Madhusudan Sharma

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

1. What will be the behavior of the Liferay Infrastructure on Liferay PaaS when a Headless API is called via 'Postman' or any other third-party system while a deployment is going on?

2. Will the requests always be served, or will they fail or be diverted to another pod when one is deployed?

Environment

  • Liferay DXP 7.1
  • Liferay DXP 7.2
  • Liferay DXP 7.3
  • Liferay DXP 7.4

Resolution

    • During the deployment, it’s expected to see minimal downtime as the traffic should be routed to the healthy backend services. Also, by default, the services in Liferay Cloud are pre-configured to use the RollingUpdate strategy, it will allow deployments to take place with zero downtime by incrementally updating instances with new ones.
    • For the requests that pass through the external load balancer have the following route ELB(Ingress) -> Nginx -> Haproxy -> Liferay, the client session will be maintained as a sticky session at HAProxy and then passed to the healthy backend service if one of the backend services crashes/stops due to some reason.
    • However, the request goes through ILB(that comes through VPN or third-party system) or Postman doesn’t have any extra layer. During the deployment, ILB forwards the requests to the healthy backend service, the requests will be served else they will fail due to the pod scheduling and initialization as the ILB continuously performs health checks on all backends and will route them accordingly to minimize the disruption.
    • When the connection comes to Liferay through the Site-to-Site VPN, the following route is established:
      Customer premises -> GCP Firewall -> ILB (Internal Load Balancer) -> Endpoints (liferay, database, webserver)

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?