The most basic proxy number allocation

[john290]

It looks like this at a high level: Minimal masking session data model. Each of Yelp’s Services conversations has an associated session which allows us to route messages and calls between the numbers seamlessly, while reflecting the message and call events on the conversation feed. How to Scale Phone Masking without Breaking the Bank? The diagram above is a good high-level outline for how phone masking works. But in reality Yelp connects hundreds of thousands of businesses and customers every month, and this model requires that we allocate one number for every connection that we facilitate.

The most basic proxy number allocation strategy is to assign a unique number lebanon mobile phone numbers database for every masking session. This can quickly get prohibitively expensive, not to mention that phone numbers are a finite resource and even the telephony API provider couldn’t provide us with that many numbers. There is a solution though, and it is 2-fold: recycle and reuse. In the following few sections, we walk through several possible phone number allocation strategies that recycle and reuse proxy numbers between sessions in various ways.


Ultimately, we arrive at the one that minimizes the size of the proxy number pool that we need to maintain in order to support our system. Phone number recycling For certain use cases such as delivery apps or connecting with your rideshare driver, the masking session needs to be relatively short lived (typically several minutes). In those situations an application can get away with having a relatively small pool of proxy numbers by using a very aggressive recycling policy.