javascript - How to build Modern front-end with non-Node.js backend? -


Normally I am backend and fullstack developer and take-lead I have been choosing Dev Dev in years.

For back-end, I have chosen typeffa stock. This makes the apps responsive and makes it easy to scale and maintain. And it's fun to code in Scala.

For Front-end, I use Angular.js, first it's Knockout. JS, YUI, Junkies, Junkies, Vanilla.

But along with Angular.js I'm really confused the problem is not only in one tool, but the way the web develops.

The aim is to tighten the application, make it more sensitive, responsive, interactive. This takes us to a one-page app Angular.js is good for it.

But.

For a modern app, it is extremely important to render the first page ASAP. For a single-page app, before solving this main template, before loading the script, launching the app, launching a routing request, asking for some resources, it can bind in a template , And then it is showing the user.

Too many networks to wait for latency! Many sequential requests come after each other.

So it takes a lot of time to see the content. Apart from this it makes it difficult to index, and limits access, through search engines (Reader mode in Safari generally does not respect the markup generated by angular.js).

Well, no one can solve the problem of searchability such as tools like preorders. OK, even if it looks ugly, but what about the first page load?

I have heard that Twitter finally made content to render on back-end, and then wrap it with scripts. how?

I have a node with the same purpose I have seen some projects on JS. They provide content to the client with the same Javascript which is actually done, and gives the result as html then it is called, feedback, responses and code, or angular. With JS But if the node.JS backend is not ours then what will happen?

Therefore the requirements are very natural:

  • Ability to render the contents (pre) on back-end
  • Page load After the wire script
  • Do not change the page content with something generated by the scripts
  • Use html5 routing for all other page views
  • node. Avoid JS, at least do not use it as main back-end technology

    Am I against the problem alone? How do you think about it?

    Here are the options for you: - A node.js middle server, for actual data and stuff A server of your choice depends on the technology. Pro, you can test it gradually before proceeding fully - write two of your template logic twice, rewrite your server once and for the client. Using nod.JS allows you to reuse logic from front-end, but Angular.js is not really node-friendly, because it is due to dependence on DOM.

    If you want the best first page to load possible, you should still see this answer:

    This will give you a static app that will give the bootstrap to the style and paths Works with you, while your corneal app loads in. Hope that helps

Comments

Popular posts from this blog

Pass DB Connection parameters to a Kettle a.k.a PDI table Input step dynamically from Excel -

multithreading - PhantomJS-Node in a for Loop -

c++ - MATLAB .m file to .mex file using Matlab Compiler -