Overview

Django REST framework

Stacks2.0K

Followers2.1K

Votes312

Hug

Stacks15

Followers55

Votes12

Django REST framework vs Hug: What are the differences?

Introduction Here we explore the key differences between Django REST framework and Hug.

Architecture: Django REST framework is built on top of the Django web framework, providing a powerful and flexible toolkit for building Web APIs. On the other hand, Hug is a lightweight and fast Python web framework designed for developing APIs quickly and easily, focusing on simplicity and performance.
Serialization: Django REST framework uses serializers to convert complex data types like querysets and model instances to native Python data types that can be easily rendered into JSON, XML, or other content types. Hug, on the other hand, relies on Python's native type annotations to automatically handle serialization and deserialization of data without the need for explicit serializers.
Routing: Django REST framework uses class-based views and routers to define URL patterns and route requests to appropriate views. In contrast, Hug uses decorators to define routes directly on the functions or methods that handle the requests, making it more concise and readable.
Middleware: Django REST framework provides a middleware layer for processing requests and responses before they reach the view or after the view has generated a response. Hug does not have a middleware layer but allows developers to define pre- and post-request hooks to handle common processing tasks.
Authentication: Django REST framework comes with built-in support for various authentication methods, including session authentication, token authentication, and OAuth. Hug, on the other hand, is agnostic about authentication and leaves it up to developers to implement their own authentication logic based on their specific requirements.

In Summary, Django REST framework and Hug differ in their architecture, serialization approach, routing mechanisms, middleware handling, and authentication support.

🔥 Trending in Microframeworks on StackShare

Hamilton Microframeworks

A scalable general purpose micro-framework for defining dataflows

Try it View Docs Alternatives

Try

Advice on Django REST framework, Hug

Kristan Eres

Senior Solutions Analyst

Jul 30, 2020

Needs adviceon

Django

Python

Flask

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?

391k views391k

Comments

Hayden

Software Dev

Jan 12, 2021

Needs adviceon

React

I'm going to do an independent study with React for school, and I'm looking to build a full-stack application. I have lots of experience with react, but everything else I'd need is somewhat foreign to me. What I'm looking for is to provide a back-end for a React application.

I'm trying to find a back-end framework that can provide and integrate with almost everything I need (database, API, authentication). I will also need to be able to host everything eventually online rather than just locally on my computer. I don't want to use something that is just click-and-go: I want to learn a lot but find something that has much built in functionality, so I don't have to completely re-invent the wheel.

Does anyone else have experience with a stack you'd recommend that is a happy medium of helpful features while still requiring you to understand and implement the functionality yourself? Something well documented (e.g., it's easy to find documentation regarding putting all the pieces together) would be great.

Thanks in advance!

68.6k views68.6k

Comments

Saurav

Application Devloper at Bny Mellon

Mar 27, 2020

Needs advice

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.

337k views337k

Comments

Detailed Comparison

Django REST framework	Hug
It is a powerful and flexible toolkit that makes it easy to build Web APIs.	Hug aims to make developing Python driven APIs as simple as possible, but no simpler. As a result, it drastically simplifies Python API development.
The Web browsable API is a huge usability win for your developers.;Authentication policies including OAuth1a and OAuth2 out of the box.;Serialization that supports both ORM and non-ORM data sources.;Customizable all the way down - just use regular function-based views if you don't need the more powerful features.;Extensive documentation, and great community support.;Used and trusted by large companies such as Mozilla and Eventbrite.	-
Statistics
Stacks 2.0K	Stacks 15
Followers 2.1K	Followers 55
Votes 312	Votes 12
Pros & Cons
Pros 67 Easy to use 65 Browsable api 53 Great documentation 51 Customizable 42 Fast development Cons 2 Reimplements Django functionality 2 Bad documentation 1 No support for URL Namespaces 0 Bad CSRF handling	Pros 4 Simple 2 Fast 2 REST 2 Elegant 2 Self documenting
Integrations
Rollbar Sentry Django Stream Kloudless	Python

What are some alternatives to Django REST framework, Hug?

Node.js

Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.

Rails

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.

Django

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.

Laravel

It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching.

.NET

.NET is a general purpose development platform. With .NET, you can use multiple languages, editors, and libraries to build native applications for web, mobile, desktop, gaming, and IoT for Windows, macOS, Linux, Android, and more.

ASP.NET Core

A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core.

ExpressJS

Express is a minimal and flexible node.js web application framework, providing a robust set of features for building single and multi-page, and hybrid web applications.

Symfony

It is written with speed and flexibility in mind. It allows developers to build better and easy to maintain websites with PHP..

Spring

A key element of Spring is infrastructural support at the application level: Spring focuses on the "plumbing" of enterprise applications so that teams can focus on application-level business logic, without unnecessary ties to specific deployment environments.

Spring Boot

Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration.