When Serguey Shinder’s team retired an order-history system, seven direct database consumers were missing from the handover and architecture inventory. The account’s practical warning is that a list of an application’s supported interfaces may not reveal every system, workflow, or spreadsheet that actually reads its database.
What happened when the order-history system was retired?
In a first-person DEV Community article, Serguey Shinder says the team spent eighteen months planning a migration and gave departments ninety days’ notice before shutting down an order-history system. By the following Monday afternoon, seven things had broken. According to Shinder, none depended on the application the migration team had spent those eighteen months replacing; each connected directly to the database.
As an Amazon Associate I earn from qualifying purchases.
Shinder says those connections were missing from handover materials, architecture diagrams, and migration workshops. The article’s accessible posting label says “Sep 20” but does not establish a year. This is Shinder’s account of one organization’s experience, not an independently verified incident report or evidence of how common the problem is.
What was reading the database?
Shinder identifies seven consumers that the team had not listed:
#1 Best Overall
- A sales commission calculation used to work out commissions.
- A logistics partner’s weekly reconciliation that depended on the data.
- A credit-check step in a workflow tool.
- A warehouse label printer.
- A dashboard built in 2018.
- A monthly regulatory extract.
- A finance manager’s spreadsheet on their machine, connected to the database and refreshed weekly since 2016.
The examples span departmental work, partner operations, reporting, equipment, and a locally maintained spreadsheet. Their common feature in Shinder’s account is the connection path: they read the database directly instead of going through the application, its interfaces, or its support team.
Why did the inventory miss them?
Shinder attributes the blind spot to limited application reporting, a database that was reachable over the network, and read-only credentials that had been shared over many years. The author says each access grant met a real need when it was made, but those connections had become dependencies outside the application team’s view.
Rank #2
An application-centered inventory can document the interfaces the team designed and supports without capturing every way data is actually accessed. In this story, direct database logins were the clue to those less visible routes.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →How did the team recover?
Shinder says the team restored database access in read-only mode for eight days, then spent nine weeks rebuilding the consumers. These are durations reported by the author for this incident; the article does not provide independent verification.
For later system retirements, Shinder says the organization began reviewing database logins for a full quarter. The author’s stated reason was that a month might miss month-end work, while a quarter could include a regulatory cycle. Shinder reports that three uses of this approach found eleven consumers, then three, then nineteen. Those counts are the author’s account, not an audited or generalizable dataset.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What can a retirement team take from the account?
Shinder describes two organizational practices that followed: reviewing database logins over a full quarter before retirement, and requiring direct-access requests to name an owner and an expiry date. The author says the registration is reviewed when an owner changes role. These are practices reported from one organization, not universal requirements or a formal standard.
Rank #4
- HP ProLiant DL360 G7 8B Server
- 2x X5650 2.66GHz 12-Cores Total
- 32GB RAM / 8x 146GB 10K 2.5in SAS Hard Drives
- P410 w/ 512MB
- Look beyond application diagrams. Ask which people, jobs, devices, partner processes, and files connect to the database itself.
- Review access across relevant cycles. Shinder’s quarter-long review was intended to include month-end and regulatory activity; the appropriate observation period depends on the system’s actual work cycles.
- Make direct access accountable. Recording an owner and expiry date can make it easier to find a responsible contact when an unfamiliar connection appears.
Shinder’s closing point is: “An application’s supported interfaces are what we designed. Its real interfaces are whatever anyone ever found a way to connect to, and the only honest inventory of those is the connection log, which almost nobody reads until the week they need it.”
Recommended Free Tools
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
