Django vs Hasura

Overview

Django

Stacks38.7K

Followers34.8K

Votes4.2K

GitHub Stars85.6K

Forks33.2K

Hasura

Stacks343

Followers634

Votes144

GitHub Stars31.8K

Forks2.8K

Django vs Hasura: What are the differences?

Architecture: Django is a full-stack web framework written in Python that follows the Model-View-Template (MVT) architecture pattern. Whereas Hasura is a GraphQL engine that provides instant Real-time GraphQL APIs on new or existing databases with built-in authorization without any changes to existing data models.
Integration: Django requires the manual configuration of APIs and integrates with GraphQL through the use of third-party libraries like Graphene. On the other hand, Hasura natively supports GraphQL and simplifies API creation by automatically generating CRUD API endpoints for PostgreSQL databases.
Real-time capabilities: Django does not have built-in support for real-time capabilities and requires additional technologies like WebSockets for real-time updates. Hasura, on the other hand, provides real-time capabilities out of the box through GraphQL subscriptions, enabling instant updates to clients when data changes in the database.
Authentication and Authorization: Django comes with in-built authentication and authorization systems that need to be configured for API endpoints manually. Hasura includes role-based access control and provides fine-grained permissions at the field level in GraphQL queries to secure API endpoints effortlessly.
Data Layer: Django requires ORM mappings and manual queries to interact with the database. Hasura abstracts the data layer and provides a GraphQL abstraction on top of the database, allowing developers to interact with the database using GraphQL queries without dealing with complex SQL queries.
Ease of Use and Learning Curve: Django is a robust framework with a steep learning curve due to its extensive features and configurations. Hasura, with its simplicity and ease of use, has a relatively lower learning curve, making it more beginner-friendly for developers looking to adopt GraphQL in their projects.

In Summary, Django and Hasura differ in their architecture, integration capabilities, real-time features, authentication and authorization mechanisms, data layer abstraction, and ease of use for developers.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Django, Hasura

Felipe

May 24, 2020

Decided

Since I came from python I had two choices: #django or #flask. It felt like it was a better idea to go for #django considering I was building a blogging platform, this is kind of what #django was made for. On the other hand, #rails seems to be a fantastic framework to get things done. Although I do not regret any of my time spent on developing with #django I want to give @{#rails}|topic:null| a try some day in the future for the sake of curiosity.

438k views438k

Comments

Sandeep

Jun 13, 2020

Needs adviceon

Python

JavaScript

Jinja

I have learned both Python and JavaScript. I also tried my hand at Django. But i found it difficult to work with Django, on frontend its Jinja format is very confusing and limited. I have not tried Node.js yet and unsure which tool to go ahead with. I want an internship as soon as possible so please answer keeping that in mind.

599k views599k

Comments

Ing. Alvaro

Software Systems Engineer at Ripio

May 21, 2020

Decided

Decided to change all my stack to microsoft technologies for they behave just great together. It is very easy to set up and deploy projects using visual studio and azure. Visual studio is also an amazing IDE, if not the best, when used for C#, it allows you to work in every aspect of your software.

Visual studio templates for ASP.NET MVC are the best I've found compared to django, rails, laravel, and others.

524k views524k

Comments

Detailed Comparison

Django	Hasura
Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.	An open source GraphQL engine that deploys instant, realtime GraphQL APIs on any Postgres database.
-	Stack-agnostic; Cloud-agnostic; Git push to deploy; Pre-configured API Gateway; Instant GraphQL or JSON APIs; Out-of-the-box Auth APIs with UI Kits; Filestore APIs with access control; Deploy custom code
Statistics
GitHub Stars 85.6K	GitHub Stars 31.8K
GitHub Forks 33.2K	GitHub Forks 2.8K
Stacks 38.7K	Stacks 343
Followers 34.8K	Followers 634
Votes 4.2K	Votes 144
Pros & Cons
Pros 678 Rapid development 488 Open source 426 Great community 380 Easy to learn 277 Mvc Cons 26 Underpowered templating 22 Underpowered ORM 22 Autoreload restarts whole server 15 URL dispatcher ignores HTTP method 10 Internal subcomponents coupling	Pros 23 Fast 18 Easy GraphQL subscriptions 16 Easy setup of relationships and permissions 15 Automatically generates your GraphQL schema 15 Minimal learning curve Cons 3 Cumbersome validations
Integrations
Python	Kubernetes PostgreSQL Docker GraphQL

What are some alternatives to Django, Hasura?

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.

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.

Heroku

Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling.

.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.

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.

Clever Cloud

Clever Cloud is a polyglot cloud application platform. The service helps developers to build applications with many languages and services, with auto-scaling features and a true pay-as-you-go pricing model.

Related Comparisons

Django vs Hasura: What are the differences?

Architecture: Django is a full-stack web framework written in Python that follows the Model-View-Template (MVT) architecture pattern. Whereas Hasura is a GraphQL engine that provides instant Real-time GraphQL APIs on new or existing databases with built-in authorization without any changes to existing data models.
Integration: Django requires the manual configuration of APIs and integrates with GraphQL through the use of third-party libraries like Graphene. On the other hand, Hasura natively supports GraphQL and simplifies API creation by automatically generating CRUD API endpoints for PostgreSQL databases.
Real-time capabilities: Django does not have built-in support for real-time capabilities and requires additional technologies like WebSockets for real-time updates. Hasura, on the other hand, provides real-time capabilities out of the box through GraphQL subscriptions, enabling instant updates to clients when data changes in the database.
Authentication and Authorization: Django comes with in-built authentication and authorization systems that need to be configured for API endpoints manually. Hasura includes role-based access control and provides fine-grained permissions at the field level in GraphQL queries to secure API endpoints effortlessly.
Data Layer: Django requires ORM mappings and manual queries to interact with the database. Hasura abstracts the data layer and provides a GraphQL abstraction on top of the database, allowing developers to interact with the database using GraphQL queries without dealing with complex SQL queries.
Ease of Use and Learning Curve: Django is a robust framework with a steep learning curve due to its extensive features and configurations. Hasura, with its simplicity and ease of use, has a relatively lower learning curve, making it more beginner-friendly for developers looking to adopt GraphQL in their projects.

Django vs Hasura

Overview