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 4 years ago.
Improve this question
I'm currently building a website where vendors from my city can authenticate and post their products, so users can search and buy them.
I started building the website with Django; in the meantime, I was taking a beautiful ReactJS 30+ hours online course and learning how much you can do with it: not only pure frontend, e.g. Routing, GET/POST requests, Forms and validation, Authentication. My initial idea was building the website with Django Rest (backend) AND React (frontend),.
But now I have a question:
Can I build my buy&sell website with React ONLY? (maybe using some pre-made backend networks like Firebase to save/fecth data to/from a database, to save time).
In your opinion would I need some backend functionalities which would be impossible/inconvenient to implement with React, Firebase or other services? Please consider that I'm talking about a quite standard buy and sell website with authenticated vendors and buyers.
Thank you very much for any advice.
While you don't need to use Django, you do need to use some backend framework to connect to your database or data store. So, to answer your main question directly, you probably need some other backend system to serve your data, manage authentication tokens, etc.
Django makes it pretty simple to wire up to a REST API (Django REST Framework is my preference, too), but you might be able to get everything you need done with NodeJS, and without Django.
Even still, you're looking at some type of backend, even with NodeJS and a simple NoSQL datastore.
I think you're on the path of least resistance by using Django, DRF, and React, and with a robust database like PostGreSQL.
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
Im new to web development and trying to learn APIs through Django Rest Framework. I am actually confused about why we actually need to build an API. For example, I've seen tutorials of creating blog APIs, where it returns the posts and its info. Why would we need an API for that? We can simply create regular Django views to do the same. I've heard that APIs only provide the 'data', but I can also obtain data from regular Django. So why would you install a totally new 'sub' framework to do these for you?
Suppose you want to build a mobile application that serves some blog posts. have you thought about how you are going to fetch the blog posts from a back-end.
Take the case of instagram, the app fetches images,comments and tags from the django backend in the form of json data and can display relevant data on the application. in short, APIs can be used when the backend and frontend technologies are different and they can communicate through APIs
The biggest reason to use Django REST Framework is because it makes serialization so easy!
see this medium post
https://medium.com/#BennettGarner/build-your-first-rest-api-with-django-rest-framework-e394e39a482c
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 3 years ago.
Improve this question
I want to make an e-commerce web app, where at the backend I am using Django and Django Rest Framework.
I want to use React, Redux and React-Router with axios library at frontend. I found-out that these are two other framework for React i.e. Nextjs and Gatsby.
Now, Which one will be better for me to make an e-commerce web app between Nextjs and Gatsby?
And, Is it necessary to use Redux, React-Router with Nextjs and Gatsby?
It all depends on, what are the important performance related features you want to have in your app? I assume you have the basic understanding of how these both frameworks work. Still, I'll try to make it as brief as possible.
NextJs uses Server-side rendering(SSR) which is good for your SEO and initial site load. It uses a concept of pages, meaning each page is in itself a route. So you don't need to implement React-router separately. It has it's own routing mechanism which can be found in here.
Gatsby is a static site generator tool. A static site generator generates static HTML on build time. It doesn’t use a server. Gatsby uses GraphQL which is a query language and if you’re familiar with SQL, it works in a very similar way. Using a special syntax, you describe the data you want in your component and then that data is given to you.
The fundamental difference is, NextJs requires a server to be able to run. Gatsby can function without any server at all. Gatsby just generates pure HTML/CSS/JS at build time, whereas NextJs creates HTML/CSS/JS at run time. So each time a new request comes in, it creates a new HTML page from the server.
And yes Redux implementation is consistent across these platforms and other state management. Though the Gatsby needs some plugins to get started with it. NextJs setup is similar to create-react-app's. And it entirely depends whether you want to go with redux or not. It has a specific use-case. Nowadays, you have partial solutions for these use-cases i.e contextAPI, hooks etc. But still you need redux for many others, where these limited solutions won't work.
So, If your back-end is in GraphQL, I would recommend to look into Gatsby, it provides some of the powerful solutions for front-end. That said, I would recommend you to go on with NextJs, if you are using any other back-end architecture. I myself had implemented an e-commerce site in NextJs and I must admit It was a great working experience for me.
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 am learning Django to develop api, but I find that most of the tutorials on the web are all use Django Rest Framework. Does it really need this framework to develop restful apis? Can I develop restful apis without Django Rest Framework
Of course you can develop a rest API without DRF - a rest API is just a set of urls mapped to views that take HTTP requests and return HTTP responses, period. Now since most often "rest API" implies JSON as the default input and output format and a proper use of HTTP verbs, some specific kind of auth etc there are some repetitive tasks that can be factored out - either rolling your own mini-framework, using an existing lightweight one like restless, or trying to find your way in the 800-pound gorilla DRF.
Of course, you can but why, when Django Rest Framework does the work for you ? If you wanna learn how it's working just use Django Rest Framework and watch the sources code of it.
Surely you can develop REST API with django, Django Rest Framework isn't part of Django project its a third party tool which facilitate faster API development. DRF takes care of lot of stuff which you need to take care by your own otherwise like.
Handling token
Authorization
Authentication
Serialization & Deserialization of dataobject
likewise many other.
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 3 years ago.
Improve this question
I'm working as an apprentice for a software company in Germany. The most time I work for projects with Visual Basic for Application (Excel). For my finals I need more practice in modern languages.
I like to build a web-application for free, can be a little project or something bigger, the important thing is that I learn a few things about planing a project, speaking with the customer about the project and build the application.
Why Python and Django?
Aside from VBA, I learned Python for my own projects. But writing application for myself is not the same like working for a customer.
Best Regards,
Tobias.M
You can get better answers from developers so ask your question on stackexchange.
Stackoverflow.com is the place where you can ask programming code related stuff.
You asked so here is your answer :
Big companies using Django:
Google
Youtube
Instagram
The Washington Post
Spotify
Pinterest
reddit
Dropbox many more.
Why Django:
The Web framework for perfectionists with deadlines.
Admin Panel by default
Create complex and database-driven applications
Free Open Source
Scalable
Secure
Projects :
Todo App
Messenger App
Authentication System with Email Backend
Blog
Blog with different level permissions
Django Projects for practive
Get started with Django projects
Further Reading
Top 10 Django Apps and Why Companies Are Betting on This Framework
Why Django is the Best Web Framework for Your Project
20 Advantages of Doing Web Development with Python and Django
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
Why is Microservice Architecture better than monolithic architecture? I know the answer will be because the microservice architecture is more scalable and each service is independent of each other etc.
My following question is: should we build using Flask or Django REST Framework?
I have also heard of a framework know as Falcon as per there documentation seems good enough.
Microservices is an architecture, not a web* framework choice
I don't think whether your app turns out to be a monolith or a microservice depends on the web framework that you are using (e.g. Django or Flask)
*Unless we're talking about frameworks specifically built to deal with managing microservices (e.g. to facilitate service discovery) web frameworks like Django or Flask are pretty equivalent (input HTTP request, output HTTP response)
Maybe their perceived popularity in a given use case (e.g. Django monolith or Flask microservice) may suggest they are better suited for a particular deployment style, but you could a microservice with Django just as easily as you can a monolith with Flask.
For instance, if I select Flask as my web framework, and in a single Flask app/process I implement all of the services (auth, admin, reporting, payroll, marketing, billing, messaging, search etc), where everything communicates on the code level, then I'd end up with a monolith.
On the other hand, if for instance I take Django, and divide my services into several small Django deploys, and make it so they only communicate through well defined HTTP contracts, and can be updated/deployed independently, then I'd end up with a microservice.
Bottom line is, a microservice is more than just the web framework you use, so use whichever one you like the most, until you have more specific requirements and e.g. 3rd party libs that are useful to you and are only available for a given framework but not the other.