Challenge
The organization operated at 20-year ERP with fragmented tooling and unclear ownership between security, platform, and application teams. Incidents were detected late; changes lacked measurable acceptance criteria.
Legacy ERP Modernization with Domain-Driven Design
The organization operated at 20-year ERP with fragmented tooling and unclear ownership between security, platform, and application teams. Incidents were detecte…
Client profile
- Sector
- Manufacturing
- Scale
- 20-year ERP
Related service
/services/app-developmentEngineering approach
Arekan mapped trust boundaries, data flows, and failure modes before writing code or rules. We ran staged pilots with rollback plans, defined SLOs for detection or retrieval quality, and aligned deliverables to audit evidence requirements.
Solution
We implemented production-ready components using .NET, React, PostgreSQL with infrastructure-as-code, monitored rollouts, and handover runbooks. Customer identities remain confidential; this case reflects a composite of anonymized enterprise engagements.
Implementation process
- 1.Discovery and asset inventory
- 2.Architecture design and threat modeling
- 3.Pilot implementation in staging
- 4.Production rollout with canary validation
- 5.Handover, training, and continuous improvement roadmap
Results
-62% average reduction
Detection / response MTTR
-41% in first 90 days
False positive triage volume
-55% manual effort
Audit evidence preparation time
99.97% maintained
Platform availability during migration
Technologies
.NETReactPostgreSQLRedis
Stack selected for interoperability, operability, and audit evidence.
Customer identities are confidential. Metrics represent anonymized composite outcomes from Arekan delivery work.