In May 2007, Drew Houston incorporated Evenflow, Inc., laying the foundation for a cloud synchronization platform born out of everyday academic frustration. While studying at the Massachusetts Institute of Technology, Houston grew tired of repeatedly forgetting his USB flash drive. To solve the problem of managing physical memory drives across different machines, he began writing code for a service that would automatically keep files identical across multiple computers.
The Forgotten Flash Drive and a Screen Recording
To demonstrate how the early software functioned, Houston published a simple screencast demo video. The video caught the attention of Arash Ferdowsi, who was impressed enough by the product's design to join Houston as a co-founder. In its earliest operating phase, trademark disputes forced the team to host the service on the temporary domain getdropbox.com. The startup operated under this web address until October 2009, when it acquired the domain dropbox.com and formally renamed Evenflow, Inc. to Dropbox, Inc.
Delta Sync and Local Ports
Creating a synchronization system that felt seamless required solving significant network bandwidth constraints. Rather than re-uploading an entire document every time a file was modified, Dropbox implemented a delta sync mechanism. Under this system, when a file was altered, the software detected the changed portions and uploaded only those modified pieces instead of re-transmitting the entire file. To accelerate speeds on shared local networks, Dropbox engineer Paul Bohm created a LAN synchronization protocol in 2010. By broadcasting over UDP port 17500, the proprietary protocol allowed computers on the same local network to discover one another and sync files directly without relying on external cloud servers.
Rewriting the Backend: From Python to Go
As user sign-ups grew rapidly, the service encountered performance bottlenecks in its underlying codebase. Originally, both the desktop client apps and the server backend were written entirely in Python, a language that allowed the early engineering team to build and iterate quickly. However, handling millions of active connections placed heavy stress on Python's execution model. In July 2014, Dropbox began migrating its performance-critical backend infrastructure to Go. Switching to Go allowed engineers to handle massive concurrent traffic far more efficiently while reducing CPU memory overhead.
Building Magic Pocket
Alongside its backend software rewrite, Dropbox addressed a critical infrastructure bottleneck. Since its early days, the platform had relied entirely on Amazon S3 storage to host user files. However, as stored user data expanded toward massive scales, hosting everything on third-party servers created major long-term cost and technical constraints. Between 2014 and 2016, Dropbox migrated its core data off Amazon S3 onto custom-designed hardware called Magic Pocket. Building its own storage architecture gave the company direct control over server design, disk density, and data management. By moving off third-party cloud infrastructure onto its custom Magic Pocket hardware between 2014 and 2016, Dropbox anchored its ability to independently scale file storage for hundreds of millions of users.
Cover: AI-generated editorial illustration; not a documentary photograph.
Source: History of Dropbox
SIGNAL TITANS
.jpg){kind=link}
Leave a Reply