How to understand the relationship of Nodejs, SPA and API? [closed] - javascript

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
Recently I attended a presentation of SPA/API/Nodejs, it looks good, so I start to google a lot and try to figure out, but get confused more.
It seems that in a SPA website, when use click, for example, a user's profile, it will call some API like http://example.com/profile/username and get a JSON data and will be displayed.
And I found a lot of frameworks, express.js/meanjs/Mojitojs/angularjs/reactjs and so on. really get lost.
So I'm going to develop a website, which will not be a SPA, but I really like Nodejs, so I'll use nodejs and i also like the idea of API to get data and display.
Can you recommend some framework to start?

SPA Frameworks: AngularJS, React.js
Node.js Webserver frameworks: Express.js, Meteor, Sails.js
You can also check Yeoman generators which help you to create a project skeleton.

Related

Which is the best way to make web application? [closed]

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 5 years ago.
Improve this question
I'm new to web development and I want to make some small web applications like a video downloaders, an document converter, and that sort of apps. I know that I can use either a JavaScript framework (react, vue, or angular) or php (laravel) but I'm confused which one is best suited for this situation.
I don't know if the this is the right place to ask this kind of questions but I want to know your opinion, so should I go with JavaScript or go the php route? I'll appreciate you help guys and thanks.
This is a very subjective question. Personally I'd recommend NodeJS or PHP as I'm not a big fan on PHP for my own subjective reasons.
My recommendations:
NodeJs: Great ecosystem, lots of shared knowledge
Use Webstorm from Jetbrains
Learn about docker, use it and make your deployments easy
Use something like Heroku until you establish it's limitations for you then you'll be better equipped to understand why you want to host another way.

Web development [closed]

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
First of all hi to all, I am new at web development and I have some questions. I have started a web site few weeks ago(html,css,js) and now I don't know how to continue. what is the next step for my project and how can I practice without publish it in a server? Nowdays I am learning php and ruby but it is more complex to understand the back end of a web site.
Since you have already started a website, add more functionalities to it. This way, you can enhance the project and at the same time learn new things as you develop. For example, if the project is in HTML, learn Bootstrap and implement the same to the project. You can publish various versions of the project. If you do not wish to publish, you can work on it locally too.
You mentioned that you are learning PHP. Why not just throw in some data to the HTML using PHP and perform some CRUD operations on it? That would be a great way to learn!
https://www.w3schools.com/ is a great website to learn.
Wish you Goodluck and I hope I helped!

Is there any advantage to use the Mantra.js architecture framework? [closed]

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 6 years ago.
Improve this question
Meteor.js integrates well inside a Mantra.js architecture, but does it have advantages since it slows the running of my requests.
For instance a dummy request in GraphQL (get a random string from the server) runs in few ms using Apollo Client and 1 second and more using Mantra.js (exact same request wrapping Apollo stack).
It only depends what kind of project you want to work on.
Mantra.js is an architecture framework for Meteor.js, that means :
it helps a developer to follow the creation and development of its modules corresponding to the Mantra framework. The developer is free to use any kind of front-end library he/she wants, any Data Query and Client caching he wants, but in my opinion, it doesn't really improve the quality of the code. Someone can organize a project with own rules and it can be maintainable easily.
So if your team is comfortable with your code structure you definitively don't need something like Mantra.js.

Model-View-Controller Pattern in Node.js [closed]

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 6 years ago.
Improve this question
What's first thing to do in MVC pattern? In CodeIgniter, we're supposed to build Model first, then Controllers but I've read somewhere build first View.
So, building MVC app: What I need to build first, What modules I need (Using Express.js framework)?
Thanks <3
As a beginner it is common to have issues like these. Well like most of the frameworks node.js also has models,views and controllers.
You can build your models using mongoose(No sql) https://github.com/Automattic/mongoose
or sequalize(for mysql/postgesql etc) http://docs.sequelizejs.com/en/latest/
for views node.js supports templating engines like jade and ejs
and as you already know you may put your business logic in controllers
Here is a detailed example to get you started http://scottksmith.com/blog/2014/05/05/beer-locker-building-a-restful-api-with-node-crud/
hope it helps :)

Is it a good idea to develop two separate node application for serving webservice and for consuming webservice to render it on browser? [closed]

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
If we are running two different node instance one of each purpose( webservice engine/data engine and webservice consumer) will it be good or keeping both the purpose in same application will be better ?
Yes it is.
One project is your API, the second project is the access to your API by web.
Maybe in the future you might need a mobile app to connect with the API or maybe the webapp technology becomes obsolete and you might need to replace it for another modern technology, so that you don't have to change your API.

Categories