I suspect I'm going to learn a lot about what not to do through this
experience. Really, I just wanted to know if golang's concurrency features
could be used to make search faster in this vaguely defined scenario and
maybe if it makes sense to. The latter part of the question will be
determined
This certainly helps me think about the problem/solution better. Thank you!
On Monday, March 26, 2018 at 4:50:01 PM UTC-7, Andre Scholtz wrote:
>
> Hi Chris,
>
> I am not sure that you have provided sufficient information for a good
> response. The performance of your search will depend a lot mor
As Andre noted, I don't think you have provided sufficient information.
I'd go further: *Stop*, Determine what you (and your developer) need to
know.
Decide what you want, and write a specification. If you have to ask
"specification for what", make a list what you don't know. Does the
speci
Hi Chris,
I am not sure that you have provided sufficient information for a good
response. The performance of your search will depend a lot more on the way
in which your data is being stored and retrieved.
For example, having multiple database queries running on the same data
would probably n
