Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
Understood the concepts of Redux and Node theoretically - planning to use one of them? both? not sure - How do they compare to each other ? When creating a new app (using React for Example) - can we use both of them? or one of them should be enough? I am stuck with this question. What should be the criteria here? People with expertise with these technologies, please help.
nodejs is a library for writing server-side logic in javascript.
redux is a library for managing application state, either client-side or server-side.
For example, it is possible to build an application that uses redux to manage its state on the client. This application could then communicate to a server-side api that is built using nodejs. The server-side api could also be managing its local state using redux.
So you can see that the two technologies are not mutually exclusive, it is not nodejs or redux. Instead you can choose to use them for their respective purposes separately or in conjunction.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 1 year ago.
Improve this question
I develop an application like Whatsapp using Vuejs and Nodejs. Can I create a backend for the entire application with Socket.io? Is it possible with Socket.io Rest api? I think there should be a Rest api in parts like the login. Is it true that I prepare parts like login with socket.io? Thanks in advance.
You can use a framework like NestJs or Adonis (or many others). Those that I'm mentioning are ready to build a REST service and also use websockets (with socket.io).
It is normal to use both in a project. The socket will be an open and persistent connection to the server, in the other case the http request is a petition, so ask yourself, Does this feature need constant communication with the server or could I ask for something and thats it??
Note: You can create a whole server using only sockets (socket.io in your case) but I think that a combination of ws + http is better
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
What would be the best set of technologies to use if I want to make a desktop application which would fetch data from server through JSON (node.js with MYSQL).
Side note: Currently we are using angular.js for frontend but the client wants a desktop app and is adamant. Don't want to change anything server side.
If you want to go ahead with js itself then you might want to look into electronjs you can even combine it with other frontend techs such as Angular, React or VueJs.
Another option is NW.js.
Look into both and choose as per your requirements both have pros and cons.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
Guys i'm new in Nodejs,
please can it be used on the web like php?
First you decide what type of situation you have.
If you want to make shopping site, social network etc which use large data processing , then you go for node.js (for example linkedin is made in node.js ).
But if your website does not require much data processing in server side you can go for php.
Nodejs is little difficult to use but once you use it perfectly your website will run smooth.
Both are good languages.
Yes you can easily use nodejs as a server side language.
Nodejs is faster than php. You can use nodejs to speedup your loading speed of your website.
Because nodejs heavily use callbacks.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
At the risk of this question being closed I will ask anyway.
I have been looking at the different JavaScript Frameworks as most jobs roles seem to want:
angular.js
Knockout.js
Node.js
Whilst i can see Angualr.js and Knockout.js provides a MVC construct to the markup pages (though still not sure which one is best to use) I cannot see what is the case for node.js?
Whilst I appreciate node.js is good for real-time comms but so is Signalr as they both use long-polling.
At present I use signalr to update images on my clients.
is there any purpose to swapping this out for node.js?
Like I said this question could be voted to be closed as it may seem to be asking an opinion - and that would be an answer to me in itself as it would be down to developer choice but is there a DEFINITIVE reason to use node.js over signalr?
thanks
One reason to use node.js is code redundancy. Both the server and client run the same language, thus they may share a certain part of the codebase, meaning potentially less to write. With libraries like Browserify this process can be made a lot more transparent and writing the client-side can be almost indistinguishable from server-side development. Another opportunity this opens up is both client and server side rendering + MVC setups with, for example, rendr.js. So you can have both the fast load speeds of server-side and responsiveness of client-side rendering. If any of this will be useful naturally depends on what you are developing.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
What advantages we will get if we use MEAN.js framework over our homegrown MEAN packaging? we are not going to use angular.js (A part of MEAN.js)
Will we face any API versioning issues? Will there be any issues related versioning of packages in MEAN?
Is it really complex to use MEAN.js as compared to creating own structure to use manage APIs, etc.
I was trying to create custom MEAN stack myself, but it was only a matter of time when i realized, that MEAN is not only MongoDB, Express, Angular and Node. Just look at node modules to see how many additional things there are. Authorization(passport.js), connectors, parsers, test libraries, mailer, promieses, etc. When i was starting I didn't find these tools useful, but now I would add most of them to my custom MEAN. Thats why I use MEAN.js stack
We can't possibly know whether your configuration will work better than MEAN.js because we know neither your needs, nor your configuration. MEAN.js provides an API out-of-the-box and supports scaffolding (via yeoman) which generates files and code with a single command. I am not a huge framework enthusiast in general, but I have to admit that development became much more easier and enjoyable since we switched to MEAN.js (ditching our own custom MEAN stack).