Infosys Equinox Enterprise

For complex implementations that require extending the Infosys Equinox Commerce platform through many of its extensibility capabilities, Infosys Equinox Enterprise provides an ideal solution.

Infosys Equinox Enterprise allows for rich integration with other enterprise systems. It is important to note that even for customers who might finally choose the Infosys Equinox Enterprise option, Infosys Equinox Cloud typically is used as a starting point and way to quickly set up and try Infosys Equinox Commerce.

Find more information on enterprise hosting in our Platform in Action section.

Experience Layer

UI/UX Experience Layer with fully functional B2B and B2C reference storefronts

Business Tooling

Sprint Boot / Thymeleaf-based business tooling with Admin console for business, merchandising and catalog managers. Separate Spring boot application for each service using single admin console.

Apache Camel based orchestration allowing one services business tooling to display data from other services.

Orchestration

Apache Camel based orchestration that ties various services together. Serves as a central place for customer specific business logic and an integration point for third party or in house microservices.

Microservices

Java Spring Boot based microservices. Allow for a Spring based plugin and extension model. Third party vendor plugins can be created and deployed along side these MicroServices. May use tools internally: Rules and BPM engines, etc.

Framework

Core template used as a starting point for any microservices implementation. Includes implementations for caching, log management, etc.

Best practices configuration of how to setup and manage the infrastructure necessary to run the platform. Focus on Kubernetes/Docker deployments

Automated, customizable scripts to manage single-tenant and multi-tenant deployments.

Hosting

Self-hosted solution with dedicated codebase and dedicated environment.

Experience Layer

UI/UX Experience Layer with fully functional B2B and B2C reference storefronts

Business Tooling

Sprint Boot / Thymeleaf-based business tooling with Admin console for business, merchandising and catalog managers. Separate Spring boot application for each service using single admin console.

Apache Camel based orchestration allowing one services business tooling to display data from other services.

Orchestration

Microservices

Framework

Core template used as a starting point for any microservices implementation. Includes implementations for caching, log management, etc.

Best practices configuration of how to setup and manage the infrastructure necessary to run the platform. Focus on Kubernetes / Docker deployments

Automated, customizable scripts to manage single-tenant and multi-tenant deployments.

Hosting

Self-hosted solution with dedicated codebase and dedicated environment.

Conceptual Architecture

Extension Points

Basic Transformation of Request/Response

AWS API Gateway

Primary place for inter-service communication. Full access to existing routes to modify as necessary.

Apache Camel

Async event handling to trigger external applications.

RabbitMQ

Extension through predefined extension points. Generally using the strategy or factory patterns.

Spring Boot

Change integration with core items like DB, Cache etc.

Spring
Hibernate
Spring Data

API Gateway

Not Infosys Equinox Code

Use any gateway to accomplish

Caching
Basic Security and Whitelisting
Basic transformations and version management.

Orchestration

Create routes in Orchestration to integrate various services together.
Use various Enterprise Integration Patterns to combine client services with Infosys Equinox and other third-party services.
XML based route creation via Visualization Tools.

Event Queue

Infosys Equinox services drop Events into RabbitMQ queues.
External applications can listen for these events.
Routes can be configured at the Camel Orchestration layer to respond to these events.

Extend Core Microservices

Plugins can be written for predefined extension points.
Infosys Equinox endpoints can be overwritten with custom code.
New endpoints can be added into existing domains.

Core Framework

Cache – Out of the box we support Redis.
SQL Database (Any Sql database supported by Hibernate).
NoSQL Database (only Document based NoSql).
Messaging system (RabbitMq is the default).
Configuration – (You can use consul or etc. by introducing the plugins).