OVO如何为其基于网络的项目确定正确的技术栈
In the current technology landscape, startups are developing rapidly. This usually leads to an increase in the number of engineers in teams, with the goal of increasing the speed of product development and delivery frequency. However, this growth often leads to a diverse selection of technology stacks being used by different teams within the same organisation.
在当前的技术环境中，初创企业发展迅速。这通常会导致团队中工程师数量的增加，目的是为了提高产品开发的速度和交付频率。然而，这种增长往往导致同一组织内的不同团队使用不同的技术堆栈选择。
Having different technology stacks within a team could lead to a bigger problem in the future, especially if documentation is not well-maintained. The best course of action is to pick just one technology stack for your projects, but it begs the question, “How do I choose the best technology stack for my projects?”.
在一个团队中拥有不同的技术栈可能会导致未来更大的问题，特别是如果文档没有得到很好的维护。最好的做法是为你的项目只选择一个技术栈，但这引出了一个问题："我如何为我的项目选择最好的技术栈？"。
One such example is OVO, which is an Indonesian payments, rewards, and financial services platform within Grab. We share our process and analysis to determine the best technology stack that complies with precise standards. By the end of the article, you may also learn to choose the best technology stack for your needs.
OVO就是这样一个例子，它是Grab内部的一个印尼支付、奖励和金融服务平台。我们分享我们的过程和分析，以确定符合精确标准的最佳技术栈。在文章结束时，你也可能学会选择符合你需求的最佳技术栈。
Background
背景介绍
In recent years, we have seen massive growth in modern web technologies, such as React, Angular, Vue, Svelte, Django, TypeScript, and many more. Each technology has its benefits. However, having so many choices can be confusing when you must determine which technologies are best for your projects. To narrow down the choices, a few aspects, such as scalability, stability, and usage in the market, must be considered.
近年来，我们看到现代网络技术的大规模增长，如React、Angular、Vue、Svelte、Django、TypeScript等等。每种技术都有其好处。然而，当你必须确定哪些技术最适合你的项目时，有这么多的选择会让你感到困惑。为了缩小选择范围，必须考虑几个方面，如可扩展性、稳定性和市场上的使用。
That’s the problem that we used to face. Most of our legacy services were not standardised and were written in different languages like PHP, React, and Vue. Also, the documentation f...