Custom Integrations

Whilst Neptune DXP provides native support for several popular integration mechanism, such as REST APIs, email, notifications, database various declining or emerging approaches can still be implemented using NodeJS libraries.

Why not Connectors or Plugins?

Many multi-experience development platforms like Neptune DXP offer many external service connectors or plugins. However, to facilitate integration it runs the danger of restricting available capabilities and falling behind with the latest releases.

Instead, Neptune embraces a low code approach. It offers a direct integration with NPM’s package manager to onboard packaged libraries. You can decide which library works best for you to tackle a specific integration requirement and animate through Neptune DXP’s NodeJS server scripts. This provides flexibility because there can be multiple libraries for a particular integration.

For example, if you wish to implement a Kafka driven event-stream architecture, there nearly 600 packages to select from to aid your integration, along with complete visibility of any dependencies. You may choose a feature complete library for a complex use case or a lightweight implementation if speed matters more. A plugin approach is bound to introduce restrictions and opaqueness on dependant libraries, and it introduces another layer of complexity between your code and the library author.

Some of the more common integration use case that can be tackled with NPM libraries are the following: