The Night Client Number 37 Arrived
At 10 p.m. last Wednesday, I was still at home in Hangzhou, revising a quote package for a client. Compressed files kept popping up in WeChat, and as I stared at my computer drive, I realized the files were scattered across multiple machines. Finding the wrong version or missing a backup could mean rework at any moment. I eventually moved everything into SQLite, and some of the trouble disappeared. I had made this mistake before: I moved the files first and designed the categories later, and it was still a mess.
What It Is, and Who Is Using It
Simply put, SQLite is a lightweight database that fits inside a single file. The approach in the original article splits files into chunks, stores them in SQLite, and lets multiple machines serve the files together. Zerodha uses a similar setup for large-scale file storage. Xiaochen, a reader who runs a design studio in Shenzhen, keeps client contracts, assets, and delivery files in one database and retrieves specific versions by assigned numbers. I was drawn to the idea for the same reason: files are no longer just sitting on a desktop; every document has a fixed “seat.” It is not a replacement for cloud storage, though, and it will not shrink files automatically. If WeChat plus cloud storage already does the job, there is no need to complicate things.
What It Costs to Try It Today
The original approach is fairly engineering-heavy, so a complete reproduction is not effortless. My low-cost experiment was to spend RMB 0 on software and use one internet-connected computer. I spent two hours creating a file library with an existing database interface, then another one to two days building the upload-number-download loop. The technical barrier is knowing basic database operations and being willing to handle file splitting and backups. The first step is not buying a server; it is opening a graphical SQLite tool, creating a database file, and adding one non-sensitive test document. I got stuck here too: at first, I was not even sure what a “database file” meant. I would start with an old image rather than a client contract. There is also no urgency to try now; organizing the cloud drive folders properly can be just as valuable.
Pick an Approach That Matches Your Team Size
Just starting out: I would begin with the RMB 0 option until the file-naming and backup habits feel natural. Once the monthly volume genuinely becomes frustrating, I would consider a database.
Already working with one or two clients: I would start with version numbers, client separation, and weekly backups before setting up multiple servers, avoiding a complex system for a single order.
Scaling up: I would ask an engineer to test simultaneous reads and writes across multiple machines, recovery after file corruption, and access permissions. At that point, the budget might include RMB 200–500 for a cloud server and test storage, depending on the file volume.
I would start with one question: is the biggest time sink “not enough storage,” or “cannot find it”? If it is only a search problem, organizing the folders may be the better investment.