Project Name
Cut Oracle EBS Modernisation From 18 Months to Under 6 With Backstage Golden Paths & Dagger on OCI
Our client is a large manufacturing enterprise based in North America, running Oracle E-Business Suite as its core ERP across finance, supply chain, and manufacturing operations. The organisation hosts its infrastructure on Oracle Cloud Infrastructure, with OCI Kubernetes Engine as the target platform for cloud-native workloads and Oracle Database 19c as the data tier.
Decades of PL/SQL customisations had accumulated inside the EBS monolith, making feature delivery slow, risky, and tightly coupled to a single deployment pipeline.
With growing competitive pressure to accelerate digital manufacturing capabilities, leadership mandated a modular, cloud-native architecture, but without a standardised path for developers, every new microservice was a greenfield project consuming weeks of infrastructure setup before a single line of business logic was written.
An 18-month modernisation roadmap with no acceleration mechanism, no service catalog, and developers spending weeks on infrastructure before writing a line of business logic.
- 18-Month Modernisation Timeline Too Slow: The roadmap to migrate PL/SQL monolith components into OKE microservices lacked any acceleration mechanism, making cloud-native transformation a long-term risk rather than a viable strategy.
- No Standardised Service Creation Path: Each OKE microservice required manual OCI provisioning, Helm configuration, database integration, and CI/CD setup, taking 2–3 weeks before development could even begin.
- Manual, Error-Prone Build and Test Cycles: PL/SQL compilation, container builds, and OKE deployments were fully manual and inconsistent, leading to frequent failures and regressions.
- No Service Catalog or Ownership Visibility: With multiple EBS modules being modernized in parallel, there was no central registry for services, ownership, dependencies, or deployment status, making coordination entirely tribal-knowledge driven.
- Limited Documentation Across Systems: Both legacy PL/SQL and new microservices lacked consistent documentation, slowing onboarding and increasing dependency on informal knowledge transfer.
- No OCI DevOps Governance Integration: Deployment workflows had no structured CI/CD governance, approval gates, or audit trails, leaving releases without traceable operational oversight.
Ksolves, as an AI-first DevOps consulting services company, built a self-service modernisation platform using Backstage as the developer portal and Dagger Go SDK as the standardised pipeline engine for the EBS build cycle. The objective was to eliminate all manual infrastructure work by encoding every OCI pattern into reusable golden paths, triggered through self-service workflows.
- Backstage Golden Path Templates: Standardised templates for OKE microservices, OCI Functions, and database-connected services enable developers to provision infrastructure and pipelines in under 10 minutes, replacing weeks of manual setup.
- Dagger Go SDK Pipelines: Fully automated build, test, containerisation, and deployment workflows for PL/SQL and microservices, ensuring identical, locally testable pipelines across all services and eliminating manual deployment errors.
- Centralised Service Catalog: Auto-registration of every scaffolded service with ownership, dependencies, environment status, and live OKE health, creating a unified view of all modernised EBS components.
- TechDocs Automation: Docs-as-code approach that generates API docs, architecture decisions, and runbooks at service creation, removing onboarding dependency on manual knowledge transfer.
- OCI DevOps Governance Layer: All deployments pass through OCI DevOps with approval gates, audit trails, and full traceability from scaffolding to production release, ensuring compliance and operational control.
Technology Stack
| Category | Technology |
|---|---|
| Platform | Backstage + Scaffolder + TechDocs |
| CI/CD | Dagger (Go SDK) |
| Compute | OCI Kubernetes Engine (OKE) |
| Database | Oracle Database 19c (via Oracle E-Business Suite) |
| Registry | OCI Container Registry (OCIR) |
| Infrastructure | OCI DevOps |
From an 18-month roadmap with no acceleration mechanism to a self-service modernisation platform where new services go from template to production-ready in under 10 minutes.
- Modernisation Timeline Accelerated (18 Months → ~6 Months): Backstage golden paths and Dagger automation compress the EBS modernisation programme, enabling rapid service delivery instead of a slow, linear roadmap.
- Service Provisioning Reduced to Minutes: Full OCI stacks, including OKE, Helm, DB connections, and CI/CD pipelines, are provisioned via Backstage in under 10 minutes, replacing weeks of manual setup.
- Near-Elimination of Deployment Failures: Dagger Go SDK standardises and automates the entire build-test-deploy lifecycle, removing manual PL/SQL and release process errors.
- End-to-End Service Visibility Achieved: Backstage service catalog provides real-time ownership, dependencies, health status, and documentation across all modernised services.
- Faster Developer Onboarding: TechDocs enables self-service onboarding with complete runbooks and architecture context, reducing ramp-up time by over 80%.
An 18-month modernisation roadmap exposed the absence of a repeatable delivery model, where every service meant rebuilding infrastructure, pipelines, and documentation from scratch. Ksolves replaced this with a self-service platform powered by golden paths and automated pipelines. What once took weeks now takes minutes. Every OCI service is provisioned in under 10 minutes with built-in governance, catalog visibility, and documentation. The programme accelerates from 18 months to ~6, with reliable, scalable delivery across the stack.
Is Your Oracle EBS Modernisation Roadmap Measured in Years Rather than Months?
