Architecture
Nexus Component Architecture
Nexus uses component based architecture which helps it to manage complexity and encourage re-use.
Ease of deployment − As new compatible versions become available, it is easier to replace existing versions with no impact on the other components or the system as a whole.
Ease of development − Components implement well-known interfaces to provide defined functionality, allowing development without impacting other parts of the system.
Reusable − The use of reusable components means that they can be used to spread the development and maintenance cost across several applications or systems.
Modification of technical complexity − A component modifies the complexity through the use of a component container and its services.
Reliability − The overall system reliability increases since the reliability of each individual component enhances the reliability of the whole system via reuse.
System maintenance and evolution − Easy to change and update the implementation without affecting the rest of the system.
Nexus Integration Flow
Nexus has been designed to act as a middle layer between systems and applications both in Enterprise Application Integration or B2B integration cases. Nexus underlying integration flow is as below :
Nexus Technology Stack
Nexus technology stack is as below diagram:
Last updated
Was this helpful?