News for hackers. Stuff that matters.

A comment on A set of best practices for JavaScript projects. Parent comment

Re:A set of best practices for JavaScript projects by whatnotests on Wednesday July 05, 2017 @03:17PM (#14705323)
Interesting point.

    app/services/signup
    app/services/signin
    app/services/newsletter_subscribe
    app/services/create_report
    ...etc
In larger Rails projects I've been on, we often start with a monolith but then break it into different services to scale out.

Starting with different services at the beginning may cause some other problems: what if the boundaries between services was wrong?

[ Parent | on HN ]
Re:A set of best practices for JavaScript projects by andreasklinger on Wednesday July 05, 2017 @03:41PM (#14705530)
if the abstraction was wrong you have the same issues. no matter if you colocate files or not. most likely it is just less of a mess
[ Parent | on HN ]