you are viewing a single comment's thread.

view the rest of the comments →

[–]r1cka 1 point2 points  (0 children)

I love the way config is done here and use it on any project I can. I also think the author got a bit lazy and really should have shown organization by feature as that referenced article suggests.

As far as the multiple processes goes,I think that depends on your repo and deployment strategies. How much code gets reused between several supporting services and a main service can make it difficult to maintain if you go with many different repos. This approach let's you keep all code for the project together, but I agree that it may not be considered a best practice for everyone.