back_office_ops · workflow
Validating performance and reliability of the Dropbox Nautilus search engine
Dropbox's traffic is write-dominated—writes occur 10x more frequently than reads—requiring a search index format optimized for high-frequency mutations while still delivering low-latency query responses for millions of users.
How it works
Common implementation structure
How this type of workflow is generally built, generalized across documented cases — not tied to any one vendor's stack. Click any stage to read what happens there. Specific products that implement these stages appear in “Tools commonly seen” below.
Stage 1 · File change triggers index write
Files being created, edited, or deleted trigger writes to the search index.
Tools used
RocksDBKafkaOctopus
Outcome
Nautilus achieves target query latency of under 500ms at the 95th percentile and under 1 second at the 99th percentile, with 2X replication and automatic partition recovery ensuring full availability during failures and maintenance.
Results
Time saved500ms
Volume10x higher than reads
Grounding & classification
Source type: technical build writeup
19 fields verified against source quotes.
enterprise searchknowledge searchknowledge basemetric backednamed customerproduction runtime claimedtools describedvendor confirmedworkflow describedsoftwaretechnical build writeupback office ops