Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

question about the surveyor pattern #1

Open
ghost opened this issue Nov 1, 2020 · 2 comments
Open

question about the surveyor pattern #1

ghost opened this issue Nov 1, 2020 · 2 comments

Comments

@ghost
Copy link

ghost commented Nov 1, 2020

Hi @robiwano ,

Hope you are all well !

I was wondering if it is complicated to extend siesta with the surveyor pattern and replicate what is described in this blog post https://daniel-j-h.github.io/post/distributed-search-nanomsg-bond/ ?

The idea would be to configure rest routes binding several, probably dockerized, respondent clients and aggregate all responses into one. Maybe, using a yaml file to configure the distribution tree ?!

Do you think it is doable ?

Thanks for your inputs and insights on that.

Cheers,
X

@robiwano
Copy link
Owner

robiwano commented Nov 1, 2020

Although I'll have to understand what the pattern does, I'm not sure I'd like to integrate that kind of functionality directly into siesta, since the aim is to keep it as simple as possible, but not simpler.
That being said, since siesta can create/remove routes dynamically, I think you'd be able to build something similar upon siesta.

@ghost
Copy link
Author

ghost commented Nov 1, 2020

Hi,

Indeed, the dynamic routes features triggered my interest.

https://github.com/daniel-j-h/DistributedSearch is an implementation of the article.

As much more a gopher than c++ developer, that's why I asked the question.

I am really interested by this feature for some deep learning rest api inference aggregation. There is a real use case ^^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant