The best part here is that none of these companies started with the model. They started with the search system they already had. DoorDash kept the model on a tighter leash. Uber pushed it deeper into retrieval. That makes more sense than rebuilding a working stack just to say it uses AI.
What stood out to me wasn’t the scale, but the architectural decision. DoorDash, Instacart, and Uber Eats didn’t win by adding more microservices, they won by building shared platforms that let every new business line reuse the same infrastructure. That’s a lesson far beyond food delivery. Great engineering is often about reducing duplication, not increasing complexity.
The key distinction is whether the model interprets the query or is allowed to decide the result. For hard constraints like allergens, deterministic retrieval is not architectural conservatism; it is the product safety boundary.
The best part here is that none of these companies started with the model. They started with the search system they already had. DoorDash kept the model on a tighter leash. Uber pushed it deeper into retrieval. That makes more sense than rebuilding a working stack just to say it uses AI.
What stood out to me wasn’t the scale, but the architectural decision. DoorDash, Instacart, and Uber Eats didn’t win by adding more microservices, they won by building shared platforms that let every new business line reuse the same infrastructure. That’s a lesson far beyond food delivery. Great engineering is often about reducing duplication, not increasing complexity.
The key distinction is whether the model interprets the query or is allowed to decide the result. For hard constraints like allergens, deterministic retrieval is not architectural conservatism; it is the product safety boundary.