You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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..
The text was updated successfully, but these errors were encountered:
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!
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..
The text was updated successfully, but these errors were encountered: