We don’t need the “one-time database of all provider’s numbers” since you found that there is no way to update it due to millions of numbers and peerless restrictions. So we should have only 1 local database that should be updating each X(4,6,10… etc) hours. This database will only search for vanity numbers we mentioned before, plus we’ll add some more. It should be UPDATE, not just add newly available vanity numbers. So when we say “update” it means after let’s say 4 hours it deletes all numbers which are no longer available. Basically it is probably replacing with new results. In this case scenario, when customer will be searching a number, he won’t see any old results. Also, don’t forget that we should have a hybrid system where non-vanity numbers will be searching LIVE-Time via API from Vendors.
I hope this helps
Reply To: Pool (Database) CMike2019-12-10T00:41:51+00:00