Middleware

Enterprise Integration Middleware

The middleware acts as an integration layer that connects IBM Sterling OMS with warehouse, logistics, payment and future ERP systems. Built on Spring Boot and deployed on OpenShift, it provides a single integration backbone with built-in reliability patterns, observability and audit logging.

JavaSpring BootResilience4jOpenShiftDockerIBM CloudREST APIs
Problem

Point-to-point integrations between OMS and multiple downstream systems create fragile, hard-to-debug architectures. Each system needs its own error handling, retry logic and audit trail — duplicating effort and creating inconsistent reliability.

Solution

Centralized Java Spring Boot middleware that all integrations flow through. Provides shared circuit breaker patterns, request and response audit logging, correlation ID tracking, error handling and retry logic in one place.

Outcome

Single integration backbone for OMS ecosystem. All integration traffic is observable, auditable and resilient. New integrations can be added without rebuilding reliability infrastructure from scratch.

Key Challenge

Designing an integration layer that is genuinely decoupled from both OMS and downstream systems — so changes to either side do not cascade into the middleware or other integrations.

Active development — deployed on IBM Cloud OpenShift Integration Infrastructure

Overview

Point-to-point integrations between enterprise systems are fragile. Every connection needs its own error handling, retry logic and audit trail. This middleware provides a shared integration backbone that all OMS ecosystem connections flow through.

Systems Connected

The middleware connects IBM Sterling OMS with Odoo WMS, Fleetbase logistics, payment providers and is designed to accommodate future ERP and third-party REST services without architectural changes.

Why Spring Boot

Spring Boot provides rapid REST API development, dependency injection, configuration management, security integration and production-ready monitoring. It simplifies deployment on container platforms and integrates naturally with OpenShift operational tooling.

Circuit Breaker Pattern

The middleware implements circuit breaker patterns using Resilience4j. When downstream services become unavailable or experience high latency, the circuit breaker opens to prevent cascading failures from propagating back into OMS. This protects order processing from being blocked by infrastructure issues in downstream systems.

Audit Logging

Every integration event is logged with: incoming API request, outgoing service call, request and response timestamps, correlation ID, processing status, error details and integration execution history. This makes debugging integration failures significantly faster — every transaction can be traced end to end.

OpenShift Deployment

The middleware is containerized using Docker and deployed on IBM Cloud OpenShift. Configuration is externalized through environment variables. OpenShift manages scaling, health checks and rolling deployments — enabling repeatable, zero-downtime releases.

← Back to Projects Work with me