Asking Explanation for Frappe and ERPNext for beginners

Frappe Framework
,
1

Hey there!

Hope you guys are doing well.
I am a student still in the final year of Under Graduation.Basically I am Familiar with python frameworks like Flask,Django and some of others,But I don’t have Good knowledge about Frappe.I Googled about it got to know about this community.
Hoping for a good explanation from you guys For a Student like me who is interested in learning different frameworks.
Thank you in advance.

2

Anything in specific?

Otherwise go through the website to understand more about the framework and apps built with the framework

1 Like
3

I can give some insight. Coming from Django and Flask/FastAPI Background here are things you should know

  1. Frappe is a Framework (Frameworks are different from Libraries in that you usually write code within “Callback” for frameworks.)
  2. ERPNext is Application built using Frappe
  3. Following used to be part of “Core ERPNext” but now lives as separate “Apps”. I believe this was done mostly for having decoupled “velocities” from ERPNext
    1. HR
    2. CRM
  4. Frappe does support Postgres. On the Other hand ERPNext I believe is right now tied to MariaDB (Because there are some insane number of SQL queries that might need to be migrated over)

Similarities to Django:

  1. Has built in ORM (Object Relationship Mapping)
  2. Support for Authentication
  3. Notion of “apps” that can be installed independently
  4. Now that Django 6 has been release: Both have built in Task queue support.
  5. Admin interface from Django is called Desk in Frappe
  6. Support for Jinja templating is present (although “Default Template” for Django is bit different)
  7. Production Setup for Django & Frappe apps are almost similar. They have component overlap:
    1. Nginx
    1. Supervisor
    1. Gunicorn

Differences to Django:

  1. Frappe support multi-tenancy out of the box
  2. Both have notion of “site” but usage intention is different
  3. There is the “frontend” way of doing things (Javascript) and same set of things could be done via “backend” way (Python)
  4. The way you create models and apply migrations are worlds apart. For Django you actually have to make changes to models.py file with Frappe it is achieved by making changes in the UI
  5. Way you write APIs is different:
    1. Frappe has Resource and Method APIs
    1. For Django you need to use something like DRF or Ninja
  6. Background Tasks in Django are usually written in Celery. Frappe uses rq
  7. Way One-to-One and Many-to-Many relations are defined are way different:
    1. What a ForeignKey in Django, is Link in Frappe
    2. ManyToManyField is loosely mapped to Child Table in Frappe
  8. Frappe has following unique aspects (again from out of the Box perspective):
    1. Print Formats
    2. Email Queue
    3. Roles & Permission mechanism
    4. Hooks
  9. Django is not built using WSGI web application library like Werkzeug
  10. Routing is done differently in Frappe. There is no urls.py file - it uses routing mechanism similar to Flas/FastAPI which is usually a decorator.

Hope this helps

1 Like
4

Thnak You,That was brief and clear explanation.

1 Like