Suggestion: Plugin-style module architecture about riess.js HOT 3 CLOSED

I'm not sure I'd describe current MEAN.JS as monolithic but rather as an opinionated project scaffold and what I like about it is it's flexibility.

I understand your points but I think if you're searching for some pluggable architecture kind of framework then you're probably looking for what MEAN.io was trying to do initially (and it didn't go well for them IMO), and these days you can consult feathers for what you're describing.

I don't like this approach because it creates complexity on the core framework and turns it into something that is by-design less flexible if you try to do simple things for users, or has too many abstractions.

Another reason I don't see much value in a complete pluggable framework is that these days microservices rule, and you'd probably be keeping your services very small and business-logic oriented to the point where you wouldn't really be "managing modules" per say across different projects, but instead you'd probably be sharing libraries and externalizing core functionalities out to their own microservices (like service discovery, users, auth, config mgmt, etc).

With that said, I like mean.js's vertical modules architecture and it does allow you to compartmentalise features or capabilities into their own module which in turn has its own routes, controllers, services, tests, etc). If you build them well then maybe you can wrap them as npm libs, and this way just share them across projects and simply do a drop-in module by just "sticking it" there in the modules/ dir.

The architecture I'd like to further build-on in Riess.js for the server-side is with regards to cleaner separation of concerns (addition of repository, services), general utilities (log, error handling),while keeping it flexible.

from riess.js.

Yeah that all makes sense.

Thanks for taking the time to write out such a good response. I'm still pretty new to web development and architecture so thanks for humoring my thoughts and providing such a constructive response :)

from riess.js.

No problems, keep on challenging and asking questions it's welcomed.

from riess.js.