Need advice about which tool to choose?Ask the StackShare community!
Django REST framework vs LoopBack: What are the differences?
Developers describe Django REST framework as "Web APIs for Django". Django REST framework is a powerful and flexible toolkit that makes it easy to build Web APIs. On the other hand, LoopBack is detailed as "*An open source Node.js framework built on top of Express optimized *". A highly-extensible, open-source Node.js framework that enables you to create dynamic end-to-end REST APIs with little or no coding. Connect to multiple data sources, write business logic in Node.js, glue on top of your existing services and data, connect using JS, iOS & Android SDKs.
Django REST framework and LoopBack can be primarily classified as "Microframeworks (Backend)" tools.
Django REST framework and LoopBack are both open source tools. It seems that Django REST framework with 14.7K GitHub stars and 4.33K forks on GitHub has more adoption than LoopBack with 12.8K GitHub stars and 1.17K GitHub forks.
The3ballsoft, Uploadcare, and Crowdkeep are some of the popular companies that use Django REST framework, whereas LoopBack is used by Riley, MAJ Digital, and ProReact Systems Nordic. Django REST framework has a broader approval, being mentioned in 159 company stacks & 79 developers stacks; compared to LoopBack, which is listed in 17 company stacks and 11 developer stacks.
My journey to developing REST APIs started with Flask Restful, and I've found it to be enough for the needs of my project back then. Now that I've started investing more time on personal projects, I've yet to decide if I should move to use Django for writing REST APIs. I often see job posts looking for Python+Django developers, but it's usually for full-stack developers. I'm primarily interested in Data Engineering, so most of my web projects are back end.
Should I continue with what I know (Flask) or move on to Django?
If you want to be a Web developer with knowledge in another frontend and NoSql technology, maybe continue with Flask. However, if you want to create very fast solutions to grow up with a new business and merge these with data analysis and other tools, Django is the answer. Basically read more about the service architecture where you feel more comfortable, Microservice or Monolithic, but please will not married with any because they solve issues to different contexts.
I have just started learning Python 3 weeks ago. I want to create a REST API using python. The API will be used to save form data in an Oracle database. The front end is using AngularJS 8 with Angular Material. In python, there are so many frameworks to develop REST APIs.
I am looking for some suggestions which REST framework to choose?
Here are some features I am looking for:
Easy integration and unit testing, like in Angular. We just want to run a command.
Code packaging, like in java maven project we can build and package. I am looking for something which I can push in as an artifact and deploy whole code as a package.
Support for swagger/ OpenAPI
Support for JSON Web Token
Support for test case coverage report
Framework can have features included or can be available by extension. Also, you can suggest a framework other than the ones I have mentioned.
For starters flask provides a beautiful and easy way to create REST APIs. Also its supported by excellent beginner docs as well as a very active community. Another good thing with Flask is its widely available list of plugins which allow you to build as you go. Its also good in performance and can scale to a quite decent level. However, if you are sure your project is going to be fairly big, it would be better to start with Django as it provides a lot of features out of the box and is extremely stable in performance. Both these frameworks have support for Swagger, JWT, Coverage Report although you have to install plugins for them. Deploying both of these are fairly simple and there is huge documentation available. Django has one of the best documentations I have come across. I hope I was able to answer your queries.
Pros of Django REST framework
- Easy to use66
- Browsable api65
- Great documentation53
- Customizable50
- Fast development42
- Easy to use, customizable, pluggable, serializer9
- Python8
- Django ORM7
- FastSerialize5
- Less code3
- Easy implementation2
Pros of LoopBack
- Need a nodejs ReST-API, DB, AAA, Swagger? Then loopback11
- Easy Database Migration9
- Code generator6
- The future of API's4
- GraphQL2
- Typescript1
Sign up to add or upvote prosMake informed product decisions
Cons of Django REST framework
- Bad documentation2
- Reimplements Django functionality2
- No support for URL Namespaces1
- Bad CSRF handling0
Cons of LoopBack
- Community is slow7
- Backward compatibility1