4 ms·

Hey thanks a lot. Can you please let me explain little further about "Server side rendering" and "Pure SPA" can you tell me which would be optimum as in order t

Hey thanks a lot. Can you please let me explain little further about "Server side rendering" and "Pure SPA" can you tell me which would be optimum as in order to learn and apply. And a bit extra knowledge about this process.

mindcrime 10y ago
Server-side rendering just means generating the HTML that will be displayed by the browser, entirely on the server, and then returning it in response to some request. This is as opposed to the model where your initial request returns a minimal bit of HTML and a big load of Javascript, and from there on the Javascript dynamically re-renders the HTML based on the response from AJAX calls. This is generally described as having a "single page application" or SPA. In reality, apps can be a blend of both approaches. Which model you use is up to you. And I'm not an expert on the front-end stuff, so I wouldn't feel comfortable making a recommendation, to be honest. All I'll say is that, to me, server-side rendering is more intuitive and straighforward to implement and it's what I usually do since I'm not primarily a front-end specialist.
- dprophecyguy 10y ago
  Hey, I have choosen Node.js for Back-End and Express as the frame work because i am aiming for MEAN stack web application. Can you please guide me for the tools and tutorials from where i can be prepared for the Back End Stuff. And yeah i will go with Server-side rendering. Thanks in advance! You made my day !
  - mindcrime 10y ago
    I don't really know that stack. Probably some one else is better equipped to guide you there.
  - sova 10y ago
    Okay, well you can use Angular or Angular 2 (I would recommend sticking with Angular1) and let's see.. MongoDB, Angular 1, Node.js, Maybe some templating language for your css? Anyway, you can run node on your own machine. Are you using mac or linux or win? Did you mention? It's pretty straightforward no matter which platform now, which is nice. So you make a javascript file that node can run, you run it from the command-line, and on your computer you have the "server" running. It's got a port, so when you go to localhost:3000 or whatever you set it to be via browser you'll see your site. The next step after you make your site with Node is to get some webspace to run it. Basically you want a remote box that you can SSH into (securely command line access another box) and then clone your project (over github) or just upload it yourself. Then you run it, you make sure you have a web-server running (like apache2 or nginx) and you serve your website over the internet. If you want to add a domain, purchase a domain on namecheap.com and go to the DNS settings. Set an A Record to the IP address of your box. Viola, you've made an internets.

mindcrime 10y ago

Server-side rendering just means generating the HTML that will be displayed by the browser, entirely on the server, and then returning it in response to some request. This is as opposed to the model where your initial request returns a minimal bit of HTML and a big load of Javascript, and from there on the Javascript dynamically re-renders the HTML based on the response from AJAX calls. This is generally described as having a "single page application" or SPA. In reality, apps can be a blend of both approaches. Which model you use is up to you. And I'm not an expert on the front-end stuff, so I wouldn't feel comfortable making a recommendation, to be honest. All I'll say is that, to me, server-side rendering is more intuitive and straighforward to implement and it's what I usually do since I'm not primarily a front-end specialist.

dprophecyguy 10y ago
Hey, I have choosen Node.js for Back-End and Express as the frame work because i am aiming for MEAN stack web application. Can you please guide me for the tools and tutorials from where i can be prepared for the Back End Stuff. And yeah i will go with Server-side rendering. Thanks in advance! You made my day !
- mindcrime 10y ago
  I don't really know that stack. Probably some one else is better equipped to guide you there.
- sova 10y ago
  Okay, well you can use Angular or Angular 2 (I would recommend sticking with Angular1) and let's see.. MongoDB, Angular 1, Node.js, Maybe some templating language for your css? Anyway, you can run node on your own machine. Are you using mac or linux or win? Did you mention? It's pretty straightforward no matter which platform now, which is nice. So you make a javascript file that node can run, you run it from the command-line, and on your computer you have the "server" running. It's got a port, so when you go to localhost:3000 or whatever you set it to be via browser you'll see your site. The next step after you make your site with Node is to get some webspace to run it. Basically you want a remote box that you can SSH into (securely command line access another box) and then clone your project (over github) or just upload it yourself. Then you run it, you make sure you have a web-server running (like apache2 or nginx) and you serve your website over the internet. If you want to add a domain, purchase a domain on namecheap.com and go to the DNS settings. Set an A Record to the IP address of your box. Viola, you've made an internets.