Technical environment

J2EE architecture

The efluid core is based on a Java SE / Java EE architecture broken down into three layers:

  • thin client user interface, which is therefore accessible using a Web browser,
  • business services,
  • data access.

The native choices of efluid software and hardware architecture have been made giving preference to certain characteristics, which include:

  • respect for standards through the use of Java EE components and Open Source libraries (Apache CXF, etc.) for the application kernel,
  • portability: efluid aims to be neutral with regard to the choice of hardware architecture implemented by our customers.  The choice of hardware manufacturers may vary considerably in X86 technology in a Linux world,
  • simplicity of the architecture : the development is based on HTML 5 / CSS / JSP pages and Java code,
  • capacity to upgrade : efluid is designed to work on scalable hardware environments with variable power and number of nodes – depending on the performance results to be achieved and the level of availability required (redundant architecture, cluster, etc.) – on a high-speed storage system (SAN type),
  • Internet / extranet / intranet : efluid is designed on an Internet architecture which offers all the flexibility of use linked to this technology, to allow multi-site use on, and indirect access to the system via portals, web-service interfaces and other connection pivots to third-party ISs.  efluid is designed to allow it to adapt to all security constraints (SSL encryption, enhanced authentication, DMZ, VLAN, firewall, etc.).

Example of hardware architecture for efluid: