DDroploxindroplox.hashnode.dev·Aug 8 · 7 min readWhy the Same Request Shouldn’t Create Two Orders: Designing an Idempotent APIBuilding Droplox — Engineering Notes #10 A repeated HTTP request does not always mean that the user intended to perform the same action twice.Sometimes an order has already been created, but the clien00
DDroploxindroplox.hashnode.dev·Aug 4 · 4 min readWhy We Started Designing Our System Not Only for Successful Scenarios but Also for FailuresBuilding Droplox — Engineering Notes #9 Most features are initially designed around the ideal scenario: the user submits a request, the data is validated, saved to the database, and the system returns00
DDroploxindroplox.hashnode.dev·Aug 3 · 4 min readWhy We Stopped Using Soft Delete EverywhereBuilding Droplox — Engineering Notes #8 In the early stages of development, Soft Delete often seems like the perfect solution. Instead of physically removing a record from the database, you simply add00
DDroploxindroplox.hashnode.dev·Aug 2 · 5 min readWhy p95 Matters More Than Average Response Time: What Our First Releases Taught UsBuilding Droplox — Engineering Notes #7 During Droplox’s first internal releases, we evaluated API performance primarily by looking at the average response time. As long as the average remained low, t00
DDroploxindroplox.hashnode.dev·Aug 1 · 3 min readWhy Companies Begin to Lose Their Ability to Make Serendipitous DiscoveriesLast updated: August 2026 Many of the most important business breakthroughs rarely emerge during strategic planning sessions or after hours of meetings. More often, they happen unexpectedly. An 00