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 months ago.
Improve this question
I understand that the front end should be backend agnostic, meaning a REST API is a REST API.
Speaking to a number of developers for an upcoming project I am continually hearing that if we opt for Vue on the front end then we should use Laravel on the backend however if we use React then Express (Node) will work well.
Why would Vue.js care or even know what the back end was?
My preference is Vue + Express, as I am familiar with Node.js
I think you can see the needs of the program you are going to make, and adjust what technology is good for the program
Front-end frameworks are actually agnostic. Most would recommend you use two frameworks together because of how easy the blend is and how they've built their back-end around a front-end framework. You can keep using your Vue and Express which is not weird at all; I mean it's called a MEVN(MongoDB, Express, Vue.js, Node.js) stack.
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 11 months ago.
Improve this question
I am a big fan of SPAs. The clear separation of front-end and back-end just makes a lot of sense to me. Development in frameworks based on server-side scripting (e.g. Vaadin, JSP, ...) always felt a bit "hacky". Sure, in the case of Vaadin you get a lot of work done quickly and can limit yourself to a single programming language. But other than the "ease" of development for smaller projects, what are reasons for picking server-side scripting approaches over a SPA?
SSR is good for SEO. SPAs does not perform well when it comes to search engine optimisation. Though there are some libraries that help you overcome this drawback of SPAs, but it is bit "hacky".
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'm in the process of setting up the development environment for a new web application, that will ultimately have a mobile component added. This is being built as a React Front-end Application that will use Google Cloud Functions for the back-end.
For source control, issue tracking, project management, I'll be using GitHub.
My question is, should I try to have a separate repository for the back-end Cloud Functions and one for the React-app front-end? Or Is it just easier to have a single application/repository and have the Google Functions live in the Functions folder?
When we add the mobile component, it will be a separate application/repository..but curious if there is any benefit to try and keep server cloud functions in their own repo?
The best practice is to separate concerns, which means having your react front-end application separate from your back-end cloud Functions.
The answer to this question is opinion-based prone.
In my opinion, I would strongly recommend anyone to not start a project using separate repositories unless there is a good reason to do so.
Separating concerns in folders within a repo should suffice. See this discussion for more background.
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 7 years ago.
Improve this question
I have developed a basic web app using normal client-side code (not using angularjs) and the Laravel framework for the backend. A friend (in the software business) is joining to help me refine it and he questioned me using a PHP framework and instead says he would re-write it using AngularJS.
Is AngularJS capable of full read/write of a database to create a dynamic website? Since AngularJS is a javascript framework, I only understood that to mostly be used for front-end and a project would still need a back-end language like PHP.
Thanks,
Angular is a front-end (i.e. browser) framework - it can't run on the server without lots of backflips and hacks, and wouldn't buy you a whole lot anyway.
You could write the back end using node.js to connect to your databases and possibly get Angular running partially on the server to generate your initial pages. This is a technique known as "isomorphic javascript" (among other terms). It's an optimization, but if what you've got works I'd stick with it.
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'm thinking about building front-end of my web application with Angular for someone else to build the back-end of it later using Django or ME(A)N or something else. I know building front-end with HTML, CSS and javascript and handing it over to back-end engineer works, but I'm not sure about Angular and I'd like to be cautious. Is this a good idea, or would it be preferred that both front-end and back-end be developed simultaneously? And does it matter whether backend is Django or ME(A)N or else?
If this is not in line with Stack Overflow policy, please do me the favor of answering before closing it.
You can develop your front-end independently with no concerns about how it will be implemented.
You can use Karma and Jasmine to unit test your Front-End code by mocking your API calls with fake responses or fake logic, and you can use Protractor to run End-to-End tests on your Front-End code, again mocking the backend with fake placeholder logic.
As long as you expose certain API to communicate with the front-end, it does not matter which one you implement from a Front-End point of view.
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
When you create a project and apps with Django, the Django engine creates the initial structure.
But when creating a project that runs Django and AngularJS on the same server, what structure do you recommend and why?
At first avoid this kind of question here in Stackoverflow because it's just primairly opinion-based. Check Stackoverflow Guide to better understand the rules.
When it's about code structure, you can find like the best answer since the structure it depends of many factors (project size, team work, developer background etc). I worken on some projects using Django, Django Rest Framework and AngularJS and end up with:
if the Angular app is small app it's more convinient to follow django structure so html files in TEMPLATES and js files in STATIC
if the Angular app is more complex on term of structure, it's better to have separate App so you make both your client and server side more maintainable and in this case I will recommand Cookiecutter as structure for Django; it's one of the most used structure and for AngularJS I will recommend the famous Angular Seed.
Make sure you take the right choice ;)