Synchronous communications

Neptune DXP implements a full HTTP server processing REST and OData APIs to enable you to define a service interface for your microservice. API interactions are in real-time implementing a request-response mechanism. The use of APIs using the Neptune DXP API Designer abstracts the connectivity details to other Neptune DXP microservices, backend systems, or SaaS/PaaS service but leads to some degree of coupling as the orchestrator is aware of the functions of the component being orchestrated.

With Neptune DXP you can build a rich tapestry of synchronous orchestrations using REST APIs, such as:

Neptune DXP Client

Neptune DXP service where your Neptune DXP apps can invoke business services implemented by Neptune DXP microservices fronted by an API gateway. For example, your omnichannel Neptune DXP commerce apps may perform stock availability checks as your customers browse, add to basket, and checkout items, utilizing a Neptune DXP global inventory microservice aggregating available stock from your network of stores, warehouses, and suppliers.

Neptune DXP Service

Neptune DXP service where your Neptune DXP microservices using Neptune DXP’s built-in service discovery can leverage their capabilities, maximizing reusability. For example, you may build a Neptune DXP order management microservice that orchestrates a series of other Neptune DXP microservices handling aspects of payment, order status, or customer notifications.

Neptune DXP Client/Microservice

SAP where your Neptune DXP application server or microservices can invoke SAP functions through the Neptune DXP SAP connector. Neptune DXP excels in surfacing a wide range of SAP artifacts using the API Factory without the need for complex interfaces or bespoke web services. For example, a Neptune DXP microservice may invoke, via a REST API generated by the Neptune DXP SAP connector, an SAP Business API responsible for creating custom orders. Using the Neptune DXP API Factory, you can rapidly convert an existing SAP report into a REST API in order to report the list of open orders for the customer.

Neptune DXP Service

System to access external SaaS services or internal backend systems, with their functions exposed as a REST API. For example:

  • Neptune DXP application server compiles weather data using publicly available REST APIs.

  • Neptune DXP vendor managed inventory microservice invokes your suppliers’ stock check APIs to compile their position and feed it to your fulfillment network’s global stock availability.

  • Neptune DXP fulfilment microservice shortlists delivery options querying your carrier REST APIs.

Neptune DXP Platform Automation

To invoke Neptune DXP’s core REST APIs to automate common implementation patterns prevalent in your Neptune DXP application servers or microservices. For example, you may want to automate the creation of your microservice artifacts, such as database tables, bespoke log tables, and generate housekeeping jobs when you provision a new endpoint resource (for example, a /recommendations resource).