Indoteknik

The previous stack (CodeIgniter-based) was becoming difficult to scale and maintain. I proposed migrating to a more modern architecture using Next.js and a structured API layer over Odoo ERP to improve performance, maintainability, and long-term scalability while preserving inventory integrity and synchronization accuracy.

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. Defined explicit boundaries between each layer, introduced caching strategies to reduce ERP load, and implemented controlled background queue processing to ensure predictable synchronization flows under high traffic conditions.

• 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.

• Implemented caching strategies to significantly reduce direct ERP load and improve response times during campaigns.

• Improved campaign-time stability by reducing direct ERP dependency during traffic spikes.

• Maintained and optimized SOLR indexing pipeline to ensure reliable, fast, and scalable product search.

• 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 while keeping data propagation predictable across services.

• Balanced performance optimizations with ERP consistency constraints.

• Avoided premature microservice fragmentation to reduce operational complexity and hidden coupling.