通过自助式物流配置平台应对DoorDash的增长

DoorDash has grown from executing simple restaurant deliveries to working with a wide variety of businesses, ranging from grocery, retail and pet supplies. Each business faces its own set of constraints as it strives to meet its goals. Our logistics teams — which range across a number of functions, including Dashers, assignment, payment processes, and time estimations — seek to achieve these goals by tuning a variety of configurations for each use case and type of business. 

DoorDash已经从执行简单的餐厅送餐发展为与各种企业合作，包括杂货、零售和宠物用品。每个企业在努力实现自己的目标时都面临着一系列约束条件。我们的物流团队（包括Dashers、分配、支付流程和时间估计等多个功能）通过调整各种配置来实现这些目标，以适应每个用例和业务类型。

Although that process started with a limited set of configurations, the old system struggled to keep up with DoorDash’s growth across new verticals. The assignment team alone hosts multiple files in GitHub to maintain the burgeoning number of preferences, some of them now weighing in at more than a megabyte each. It doesn’t help that these preferences aren’t kept in standard formats; some are JSONs, others are CSVs, and still others have no format at all. Maintaining these files and updating them at the speed of DoorDash’s growth has been both challenging and risky, with multiple outages occurring because of incorrect configurations. Additionally, the current system operates with a limited set of features, reducing the speed with which new capabilities and experiments can be launched. 

虽然这个过程始于一组有限的配置，但旧系统难以跟上DoorDash在新垂直领域的增长。仅任务小组就在GitHub上托管了多个文件，以维护不断增长的偏好数量，其中一些现在每个文件超过一兆字节。这些偏好并不以标准格式保存；有些是JSON格式，有些是CSV格式，还有一些根本没有格式。维护这些文件并以DoorDash的增长速度进行更新既具有挑战性又具有风险，因为由于配置不正确而发生多次故障。此外，当前系统的功能有限，降低了新功能和实验的启动速度。

With all of that in mind, we set out to build a new logistics configuration platform that could not only meet today’s demands but could continue to scale well into DoorDash’s future growth.

考虑到所有这些，我们着手构建一个新的物流配置平台，不仅能够满足当今的需求，而且能够在DoorDash未来的增长中持续扩展。

Figure 1: High-level assignment architecture

图1：高级分配架构

Figure 1 represents a simplified, high-level version of DoorDash’s existing architecture in which users up...