Hacker News new | ask | show | jobs
by datr 3063 days ago
We considered doing something like this on a project once but we had concerns about performance. How much latency does your API proxy add in for responses with thousands of tokens?

Additionally we found that this broke any sort of database indexing. Let's presume that Lyft would need to tokenize the start and end points of journeys (otherwise it would be quite easy to de-anonymise someone) then just doing simple queries like I want to know how many journeys happen in this area either become incredibly slow or you have to have anticipated needing this type of query and providing a non-tokenized "area" field which can be indexed (but is sufficiently coarse not to leak data). Were you able to come up with any sort of solution for this issue?