DoorDashCompany

Local commerce and food delivery platform

8 things

liked

We already had lots of experience and expertise with Postgres and Apache Cassandra , so these would remain our data stores.

DoorDash keeping Postgres as a data store in the new stack

liked

We already had lots of experience and expertise with Postgres and Apache Cassandra , so these would remain our data stores.

DoorDash keeping Cassandra as a data store in the new stack

KotlinSoftware

recommended

After surveying a number of different languages, we chose Kotlin for its rich ecosystem, interoperability with Java, and developer friendliness.

Why DoorDash migrated its backend services from Python to Kotlin

KafkaSoftware

uses

We quickly agreed on gRPC as our mechanism for synchronous service-to-service communication, using Apache Kafka as a message queue.

DoorDash's new backend stack: gRPC and Kafka

gRPCSoftware

uses

We quickly agreed on gRPC as our mechanism for synchronous service-to-service communication

DoorDash choosing gRPC for service-to-service calls

ScalaSoftware

uses

this service was written in Scala mainly because Python was not a good fit for CPU-intensive tasks.

DoorDash's first microservice, Deep Red, was written in Scala

PythonSoftware

mixed

the dynamic typing nature of the language made it difficult to verify that changes didn’t have unforeseen effects at runtime.

DoorDash on the limits of Python in its monolith

DjangoSoftware

disliked

On top of that, our monolith was built on old versions of Python 2 and Django , which were rapidly entering end-of-life for security support.

Why DoorDash left its Django monolith