This page provides an overview of Infosys Equinox’s microservice-based approach for its 8 release.
The Infosys Equinox 8 release was built with a microservice architecture. Microservices are an approach to structuring software systems that breaks up the mass of a design into a set of core services, each of which is built as a standalone, deployable unit. Like many other software design approaches, microservices are a mechanism to improve the structure of a system by reducing local complexity and imposing an orderly approach to encapsulating data. By breaking the system into smaller, standalone services, we can evolve each microservice as needed by the business, and we can deploy, scale-out, and manage each microservice independently.
Note: Click on the required card below to navigate to the respective API endpoints.
Microservice-based approaches need to coordinate the work of multiple microservices into a coherent whole. Infosys Equinox uses Apache Camel-based orchestration to link the collection of microservices into a coherent system. Each service has storefront (user-facing) and administrative orchestration. For several services which combine the efforts of multiple underlying services, a composite orchestration calls these services.
Each Infosys Equinox microservice is a standalone spring boot web services exposing REST-style (Representational State Transfer) interfaces. Each microservice has its own persistence, caching, and administrative interfaces. Microservices may be deployed individually, or in clusters, according to the needs of the customer. Each microservice may be deployed as a docker and scaled using Kubernetes (automated deployment, scaling, and management of containerized applications) and related cloud-based approaches.
There are no horizontal dependencies between the Infosys Equinox microservices outside the REST application programming interface (API). Infosys Equinox applies traditional semantic versioning, and within the 8.x release provides API-level compatibility. As these APIs are declared with JSON data models, additional request and response elements may be added to existing microservices without breaking compatibility.
Because Infosys Equinox microservices provide an API-only level of integration, it is straightforward to wrapper a customer’s existing implementation of a service as a microservice and use orchestration to include it in a Infosys Equinox deployment. For example, a customer’s proprietary implementation of inventory management, or an existing ERP system can be directly referenced and integrated into a consistent solution.
TIP: Checkout our Terminology and Concepts page for terms and concepts and their associated definitions within the context of the Infosys Equinox Platform.
2022-01-10 | JP – Minor copyedit.
2019-05-01 | PLK – Minor copyedit.
2019-01-21 | PLK – Content uploaded.