Thanks, very interesting and useful!
I often find that choosing a correct architecture for an application is one of the most important tasks.

yeah, since it's an early stage decision, it's gonna have consequences (bad or good) on any other subsequent one.
Furthermore, creating substantial technical debt at this stage could be too much expensive later on!

Thanks,

My SPA development are messy not until now.

Thanks for sharing this article, now I know how to structure future applications and Im a better engineer. Thanks a lot.

ya, that's a general approach to modern front end dev. :)

Thanks Morco, its a informative article. on one of your point where you preferred to write business logic in plain javascript and not in any specific framework like Angular or React, etc, i think its a fare design decision i personally faced issues while writing Business logic in service or model layer (specific to framework) because of which framework version up-gradation, change in framework like moving from Angular to React becomes very complicated and time consuming.

On the other hand for this implementation we need to define the access protocol like how my visual (react/Angular/polymer) component will use business logic written in pure JS, how these two small pockets interact with each other etc. Do you have any viewpoint on this?

Thanks Morco. Your description of different roles each JS library helps backend developers like me come to grip to the overwhelming JS frameworks sprouting now and then. I will now read other articles on your blog now..

I'm really happy to help! 😊