Indoteknik
Rebuilt the company's ecommerce platform from the ground up, migrating from a legacy CodeIgniter stack to a modern Next.js frontend with a custom Odoo-based API layer and SOLR-powered search indexing.
Context & Problem
The previous CodeIgniter stack was difficult to evolve alongside ERP-driven catalog and inventory workflows. I proposed a Next.js storefront with a structured API layer over Odoo ERP, keeping inventory and synchronization boundaries explicit.
Approach
Led the architectural direction by initiating the migration from a monolithic CodeIgniter setup to a decoupled architecture: Next.js for the frontend, a custom API layer over Odoo ERP for business logic, and SOLR for search indexing. Separated responsibilities between layers, introduced caching strategies to reduce ERP load, and implemented controlled background queue processing for high-traffic synchronization.
Highlights
Initiated and led the migration from a legacy CodeIgniter stack to a modern Next.js-based frontend architecture.
Designed and maintained custom API layers over Odoo ERP to isolate business logic from presentation and external traffic spikes.
Introduced caching to reduce direct ERP dependency during campaign traffic spikes.
Separated storefront traffic from ERP-driven business logic during campaigns.
Maintained SOLR indexing pipelines for product search and catalog updates.
Built internal stock opname tools and synchronization flows to keep inventory data consistent across ecommerce and ERP systems.
Structured background synchronization flows to prevent race conditions between ERP updates and storefront visibility across services.
Trade-offs
Balanced performance optimizations with ERP consistency constraints.
Avoided premature microservice fragmentation to reduce operational complexity and hidden coupling.