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 2 years ago.
Improve this question
I will start developing my e-commerce website soon however, I don't have experience in backend. So I'm considering to use firebase. But my real concern is, , is firebase good option on long term? Is it easy to migrate to mongodb and node js or is it better to write my own backend from the beginning?
You should consider using firebase if the features are useful to you:
authentication
noSQL database
storage
in-app messaging
It is a good option long-term if don't hit the upper limits of the free plan for a long time. This is almost always the case for new unknown projects.
Because of the noSQL nature, switching to mongoDB is straight-forward. The real question is if you are already experienced with setting up and using node.js with mongoDB. You are better served with what you already know.
Use Firebase if you have no significant experience with the alternatives.
Related
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 2 years ago.
Improve this question
We are building a platform using microservice-based architecture. We are expecting 500K users in the next two years so for that we are thinking to use below technology stack as below:
Python - Fast API
UI - React SSR (Server Side Rendering)
Here, we found during concurrency analysis that node is faster than Fast API.
We are confused that should we go with nodeJS or Fast API (asyncio). We have more expertise in python so more leaning towards it but we do not want to bias in the selection of technology which later on creates problems for us.
So we need guidance the shall we proceed with Python to handle millions of requests using - Fast API or we should go with node?
Or If you think we can have a better technology option then above then we are open for suggestions.
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 4 years ago.
Improve this question
I am just about to make a small instant messaging server.
I am thinking of using MongoDB, NodeJS, and Redis. Do you think it is a good choice?
What do you think about the model schema?
It's really a good choice. If I were you, I'd use socket.io, node.js, and mongoDB.
you can also use mongoose which is a model-based and It's much better.
MongoDB(Mongoose) is a good choice, because when you do a instant messaging application, it's a good choice (you will need ) to store data as documents.
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
this article suggests that using MongoDB for a SAAS application that you should use one DB for each client - can this be right? http://docs.mongohq.com/use-cases/marketing-platforms.html (see bottom of page)
If so are there any occasions when it would still pay to put all clients into one DB?
I asked a similar question
Is it better to use multiple databases when you are managing independent sets of things in MongoDB?
The conclusion seems to be its not really very efficient to have multiple databases. But its still a valid way of doing things.
A more important consideration is if you want to do queries across customers for whatever reason, then your job gets a lot more difficult if they are in separate databases.
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
I've heard that node.js is really fast for applications like chats and real time apps.
I was wondering if node is a good choice to develop a forum or a q&a site like StackOverflow?
Yes it's perfectly possible, you don't have to implement your own web server like somebody said, you can just create it using something like Express (as a framework) and Mongoose (as a MongoDB ORM) or whatever you choose.
I think Node.js is a good solution for such a case because of its high concurrency (and Stack Overflow is a site where thousands of users are online in the same time probably). So yes you can achieve this with PHP, Ruby and Python etc, but I believe Node.js is a better fit (that's my opinion, based on the success stories I've heard which were based on Node).
Node isn't just a solution for building small services, here are some good examples ( https://nodejs.org/en/blog/uncategorized/an-easy-way-to-build-scalable-network-programs/ ).