Guide de communication microservices avec Liferay (Architecture entreprise)

 Les portails modernes ne sont plus monolithiques.

Aujourd’hui, Liferay sert de couche d’expérience digitale tandis que la logique métier vit dans des microservices indépendants.

La question principale devient :

👉 Comment Liferay communique avec les microservices ?

Ce guide présente les modèles utilisés en production.

📌 Pourquoi utiliser des microservices avec Liferay ?

Ancienne architecture :

Portail → Base de données → Logique métier dans le portail

Architecture moderne :

Portail → APIs → Microservices → Bases de données

Avantages :

  • Déploiement indépendant

  • Scalabilité

  • Maintenance simplifiée

  • Séparation des domaines

🖼️ Architecture globale

🧠 Modèles de communication

4 modèles principaux :

  1. REST (synchrone)

  2. Messaging événementiel

  3. Gateway GraphQL

  4. Workers asynchrones

Chaque modèle a son usage.

🔹 1️⃣ REST (synchrone)

Pour réponse immédiate à l’utilisateur.

Exemple : modification du profil.

URL url = new URL("http://customer-service/api/profile");
HttpURLConnection con = (HttpURLConnection) url.openConnection();
con.setRequestMethod("POST");
con.getResponseCode();

🖼️ Flux REST

🔹 2️⃣ Messaging événementiel (asynchrone)

Pour traitement en arrière-plan.

Exemple : upload document → traitement.

Technologies :

  • Kafka

  • RabbitMQ

Le portail ne bloque pas.

🖼️ Flux événementiel

🔹 3️⃣ Gateway GraphQL

Permet d’agréger plusieurs services en une requête.

Avantages :

  • Moins d’appels réseau

  • Frontend rapide

🖼️ GraphQL

🔹 4️⃣ Workers asynchrones

Pour traitements longs :

  • Génération PDF

  • Import massif

Le portail déclenche → worker traite plus tard.

🖼️ Workers

⚖️ Quand utiliser quoi

CasSolution
Attente utilisateurREST
Traitement lourdMessaging
Plusieurs servicesGraphQL
Long traitementWorkers

🔐 Sécurité

Utiliser :

  • OAuth2 / OIDC

  • API Gateway

  • Token propagation

  • Rate limiting

Ne jamais exposer services directement.

🏆 Bonnes pratiques

✔ Portail léger
✔ Pas de logique métier dans Liferay
✔ Gateway API
✔ Préférer asynchrone
✔ Domain-driven services

⚠️ Erreurs fréquentes

❌ Base partagée
❌ Chaînes synchrones longues
❌ Portail orchestrateur
❌ Couplage fort

🎯 Conclusion

Liferay doit être :

👉 Couche d’expérience uniquement

Les microservices gèrent la logique métier.

Une bonne communication garantit une architecture scalable.

💼 Support professionnel disponible

Si vous rencontrez des problèmes sur des projets réels liés au développement backend d’entreprise ou à l’automatisation des workflows, je propose des services de conseil payants, de débogage en production, de support projet et de formations ciblées.

Les technologies couvertes incluent Java, Spring Boot, PL/SQL, Azure, CMS, ainsi que l’automatisation des workflows (jBPM, Camunda BPM, RHPAM).

📧 Contact: ishikhanirankari@gmail.com | info@realtechnologiesindia.com

🌐 Website: IT Trainings | Digital lectern | Digital rostrum | Digital metal podium     



Comments

Post a Comment

Popular posts from this blog

Scopes of Signal in jBPM

Image
💡 Introduction Signals in jBPM 7 are a core part of event-driven workflow design. They allow asynchronous communication between process instances, making it possible to start , interrupt , or coordinate processes without direct linking. However, signals can have different scopes , which define how far the signal travels and who receives it . Let’s explore the four available scopes in detail: 🔹 Process Scope 🔹 Default Scope 🔹 External Scope 🔹 Project Instance Scope 🧩 1️⃣ Process Scope 📘 Definition Process scope signals are local to a single process instance or its child subprocesses . They are not visible outside that instance hierarchy. 📋 Use Case Used for communication inside the same process , like triggering subprocesses or event sub-processes. 🖼️ Process Scope Example Below is an example of a simple process-scoped signal. Only this process (or its subprocess) will catch this signal. ⚙️ 2️⃣ Default Scope 📘 Definition The default scope ...
Read more

OOPs Concepts in Java | English | Object Oriented Programming Explained

Image
🔹OOPS (Object Oriented Programming System) in Java Object-Oriented Programming (OOPS) is a programming paradigm that uses classes and objects to design software. It simplifies development and maintenance by applying key concepts: 📌 Class: Class   is a user-defined data type which defines its properties and its functions. Class is the only logical representation of the data. For example, Human beings in an organisation is a class like Employee. The age, name, department, salary etc. of a human being/employee are its properties, and the jobs performed by the employees in an organisation are known as functions.  The class does not occupy any memory space till the time an object is instantiated. A class is a user-defined data type that defines properties and functions. For example: Class: Employee Properties: name, age, salary Functions: work(), attendMeeting() A class does not occupy memory until an object is created. ...
Read more

jBPM Installation Guide: Step by Step Setup

  jBPM Installation Guide – Step by Step for Beginners If you are starting with jBPM (Java Business Process Management) , the first step is to set up your environment. In this guide, we’ll walk through how to install jBPM, configure it, and run your first business process. 🔎 What is jBPM? Before we dive into installation, a quick recap: jBPM is an open-source Business Process Management (BPM) suite , written in Java, that allows you to model, execute, and monitor workflows using BPMN 2.0 standards. It can run standalone , embedded in applications , or deployed on a Java EE server . 🖥️ Prerequisites Before installing jBPM, make sure you have: Java JDK 11 or later (Java 17 is commonly used) Maven 3.x (for building and managing dependencies) Git (optional, if you want to clone sample projects) A Database (H2, MySQL, PostgreSQL, or Oracle) – jBPM ships with H2 for testing At least 4GB RAM (8GB recommended for Workbench & KIE Server) 📦 Download ...
Read more