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
My friend and I are working on creating a product from scratch. We aim to build a cross platform application using react-native. We've planned to use firebase as our server hosting application.
Although, we both have fair amount of knowledge in react and have gone through some videos on react-native and firebase, mobile app development from scratch is still pretty new to us. We're having trouble to answer the following questions:
Where to start developement ?
Should we write our server in nodeJS and deploy it on firebase and my app can call the endpoints or should we connect to firebase directly from client side ?
How to setup configuration files and different environments for developement ?
These are among the many questions we have and we feel lost in this sea of infinite information.
Could anyone guide us here ? Please help me if I can frame my question in a better way.
React Native is a great place to start. With today's ecosystem lead by flutter and react, Angular has unfortunately fallen behind.
Both, Cloud functions are Firebase's solution to server instances, these create short-lived functions that do complex or secure tasks such as handle payments, delete/manage users, etc. While the bulk of your app and its logic with firebase should be handled on the client, including accessing the data so long as you have secure rules.
this depends entirely on your framework of choice but in general, there should be a build option that enables you to configure which settings to compile with.
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
I am curious with all the features of firebase, cloud functions, and client-side authentication, Firestore, etc. options, does it make sense to even use a 'backend' with a firebase web app? The reason I am asking is that I started a project with a react app and a node.js backend rest API service. I started to realize that with all of firebases features, it might make sense to scratch my backend entirely. What are everyone's thoughts? Thanks
You can use firebase directly without a backend (if it is just a simple project) but i'd recommend you to use it with a backend to be more secure, since the backend lets you check the recieved data if it is fake or not correct, also in order to hide your firebase's api key and other stuff like that, i have a firebase app on github (with front-end of react and backend of nodejs+firebase) i can leave the link of the repo if you are interested to check it out, thanks
Firebase is definitely a very good option for you. Since you are adept at using Javascript, you can use the Firebase JavaScript SDK and your backend is up and running
Google’s Firebase offers the following:
A very robust authentication service(Currently supports Google, Facebook, Twitter, Github, Email/Password and Anonymous authentication).
Realtime Database
Storage
Hosting
Cloud Messaging
Notifications
Analytics
Hope this help...
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 3 years ago.
Improve this question
I have an application that we implemented kind of a microservices type architecture. The application contains 6 services (6 Docker containers). I need to load test this application. As I don't have much experience in the testing field, I'm not sure which method to use.
Right now, I have used the Gatling Load testing application for the load test. Here, I record the testing script by start the recorder and wander around my application to record all routes. I have gone through most of the routes in that single recording in order to mimic a practical user. I thought, normally users use an application like this and I can load test with its 1000 times by editing the number of threads/users.
Later I read about API testing which we will focus on APIs. Loading each APIs with a heavy load. So, I'm confused that which testing method should I use? If we go for API testing, it will provide only how much we can scale for that particular API right? (Not sure)
Is there any issue with my method of load testing?
It depends entirely on what you hope to achieve...
If you're looking to validate that your entire application (code + production infrastructure) can handle a given load, then driving as though going through the full website is the right path.
However, if you're looking to see how a particular api scales or want to help developers explore the ramifications of changes, then you will probably want to just drive that API directly to avoid other limitations your system may have.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 5 years ago.
Improve this question
I have doing a lot of research about frontend frameworks and have decided that I would like to try Vue.js. However, I would also like to get a backend with real time "data updating". I have looked at VueFire (Vue.js + Firebase), Node.js and Feathers. It looks like Feathers has a limited amount of resources/documentation on using it with Vue while there seems to be a good amount of information on VueFire and Node.js with Vue.js.
What are the differences between those three backends?
What are the advantages/disadvantages of using one over the other?
What are the differences between those three backends?
Let's clarify a few things.
Node.js is, as defined on their website: "a JavaScript runtime built on Chrome's V8 JavaScript engine."
Firebase is a platform as a service (PaaS).
Feathers is REST and realtime API framework, a back-end framework.
VueFire is just a wrapper around the Firebase JS SDK. It makes calling Firebase more "Vue" like.
Vue.js is a front-end framework or progressive framework as the creator calls it.
With that said we're comparing Feathers and Firebase. It's clear what the difference is and the advantages/disadvantages.
What are the advantages/disadvantages of using one over the other?
Firebase lets you hit the ground running. You create your Firebase account/project and you're set to go with all the products it offers. You do not have to worry about setting up your own database layer, authentication/security, or anything. It's all set up and managed for you, but at a cost. Besides the money factor, you've also locked yourself and depend heavy on a third party and things can change at anytime without any say in the matter.
Feathers is a framework. It gives to tools to create your own Firebase platform. You're free to configure it however you want. You're in full control and it's free. However, you will have to setup your own database layer, security, and likely more.
In the end it boils down to your needs/requirements. It's best to make a list of your specific needs and see what framework or service fulfills those needs. It's useless to search for advantages/disadvantages as you will get opinion-based answers.
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.
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
my situation is the following:
I have a REST API Node.js server using MongoDB, which will serve data to the clients.
I have one web client which will fetch data from the API service and provide social authentication.
For the purposes of my question, let's assume that I have two different clients - both web apps. In this situation, who should be responsible for social authentication, sessions, cookies, etc? The user database should be shared between all clients, but I feel like authentication and API should be two separate services.
What is the most common approach in this situation?
Client will be built with AngularJS, REST API service is built with Node.js, Express, MongoDB, Mongoose and eventually Passport.js when I figure it out.
Thanks
but I feel like authentication and API should be two separate services.
If you have to ask, you don't want 2 separate services. (services meaning independent network daemons/express apps)
Start with just 2 separate modules within your single express app. You can have an auth.js module that uses passport to handle authentication and session issues and then one module file for each entity in your API. If you need more than 1000 lines of code in your auth.js file considering passport is doing most of the hard work for you, something is going wrong. Take a step back and ask for a code review.
If you want each of your 2 web apps to have it's own Express server, just factor the auth.js module out into its own shareable npm module and require it from each web app.
Splitting things out into microservices is for large team projects at scale. Stick with a single simple express server for the first several years (or forever for projects that don't support a rapid-growth startup).