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

Questions regarding Cluster.WebCrawler sample #33

Closed
michaelsync opened this issue Aug 25, 2015 · 1 comment
Closed

Questions regarding Cluster.WebCrawler sample #33

michaelsync opened this issue Aug 25, 2015 · 1 comment

Comments

@michaelsync
Copy link

I am new to Akka.NET so please feel free to correct me if I am wrong.

I understand that Cluster.WebCrawler is just a sample project (not the production code) but is it the best practice to put all logic in one main project? I think the main logic for crawling is in WebCrawler.TrackingService and Shared. As the micro-service architecture is being used in this sample, wouldn't it be better if the code that has different purpose can be separated? What I worry is that when the project got bigger (e.g. adding new cluster.uploaders ), we might end-up writing more logic in tracker and more classes in Shared project..

@michaelsync
Copy link
Author

I found that Web talk to Tracker via clustering. The logic for tracker is not in web project but in tracker. So, I guess it's not the technical limitation to put the crawling logic in tracker. I think it was a choice. I am interested to know why you guys choose that. Thanks!

@skotzko skotzko closed this as completed Oct 12, 2015
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

2 participants