How OVO determined the right technology stack for their web-based projects

Summary

OVO faced maintainability issues caused by fragmented web technology stacks, including PHP, Vue, React, Nuxt, and Go, alongside outdated documentation. This fragmentation resulted in severe context-switching costs during code reviews and prolonged onboarding times for new engineers. To establish a single primary front-end stack, the team compared React and Vue against maintainability principles encompassing operability, simplicity, and evolvability. Vue was selected because its standardized framework structure and documentation minimized architectural variations across projects. Implementation entailed creating a standardized Vue boilerplate, updating the internal UI library, and scheduling periodic upgrades for legacy React services rather than migrating them entirely.

Takeaways

1. 1

   Standardizing on a single framework allows applying security patches once across all projects rather than creating distinct patches per stack.

2. 2

   Vue was chosen over React because its framework structure and standardized documentation provide consistent patterns that reduce complexity across teams.

3. 3

   OVO elected not to migrate existing legacy services to Vue, opting instead to enforce the standard on future projects while performing periodic upgrades on legacy code.