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
Looking through the codebases, I keep wondering whether we could transfer task-service as an app to the core-service repo. Is it really necessary to run two separate django servers and databases for core-service and task-service? Wondering what y'all think. Tagging @dhimmel@awm33
The text was updated successfully, but these errors were encountered:
@dcgoss I don't have a strong opinion. I believe @awm33 saw benefits to a having a separate service. But I'll defer to you what the best way forward is.
@dcgoss@dhimmel There can be benefits to a separate service if the project grew much larger in scope. But given the projects progression over the last year, I think it's safe to combine them. Since there's a 1:1 ratio between classifiers and tasks, you could even just move the task management columns directly over to the classifier table.
Looking through the codebases, I keep wondering whether we could transfer task-service as an app to the core-service repo. Is it really necessary to run two separate django servers and databases for core-service and task-service? Wondering what y'all think. Tagging @dhimmel @awm33
The text was updated successfully, but these errors were encountered: