Isomorphic Web Application – AngularJS is possible loser by ReactJS or my MEAN stack confusing story


I am Google Fan – but seems never interesting with AngularJS.

I am anti Facebook – but seems getting interested with ReactJS.

I have been working with Java as primary server side technology, JavaScript by NodeJS seems like an alien to me

This article is not introducing about reactjs, nor comparing angularjs with reactjs

isomorphic web application

If you want to understand about isomorphic web application – visit because of shorten explanation, a lot of useful articles, links …

By 3 years, nothing else attracting me than the term “isomorphic web application – iwa”. This term is new to me, along with SPA (Single Page Application) that I have been working on for a year. The fact that most Web Development Companies in Vietnam are now interesting with MEAN stack, requesting developers must be familiar with AngularJS, NodeJs … Most Technical Leader telling much about NodeJS, despite of their explaining is about building an eco JavaScript application – both server side and client side that implementing unique JavaScript, but the confuse is while JavaScript can be executed by server side, why do we keep continue using it in client side ?

AngularJS is complete MVC framework, but needs DOM elements to bootstrap, renders HTML page. I used to wonder that pull down AngularJS running in server side, but so painful that no DOM elements within server side (do not mention phantomjs – it’s about different context, story …)

Routing – for the most MVC frameworks like Spring, Playframework, or RoR … developers are easily to recognise that happens in server side code, but weird in client side. The MEAN stack is offering both routing for client side (AngularJS) and server side (ExpressJS). Imaging that your developers discussing about routing but not determine which side.

As usual, the pipeline to server a page should be: route -> fetch -> parse -> render

The MEAN stack pipeline: route (server) -> fetch (server) -> parse (server) -> render (client) -> route (client) -> render (client – actually renders DOM). The server side could be executing one time for application lifecycle, why wasting effort to do server side routing ?

Isomorphic is a big deal, not for routing but also aiming view, data, event handling (see the discussing), developers who wanting apply ReactJS/Flux should consider about isomorphic web application.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s