quickjs VS Django

This is a fantastic approach.

BTW, it looks like the js engine is "QuickJS" [0]. (I'm not familiar with it myself.)

I like it because sqlite by itself lacks a host language. (e.g., Oracle's plsql, Postgreses pgplsql, Sqlserver's t-sql, etc). That is: code that runs on compute that is local to your storage.

That's a nice flexible design -- you can choose whatever language you want. But quite typically you have to bring one, and there are various complications to that.

It's quite powerful, BTW, to have the app-level code that acts on the app data live with the data. You can present cohesive app-level abstraction to the client (some examples people will hopefully recognize: applyResetCode(theCode) or authenticateSessionToken(), or whatever), which can be refined/changed without affecting clients. (Of course you still have to full power and flexibility of SQL and relational data for the parts of your app that need it.)

[0] https://bellard.org/quickjs/

Considering the extremes of prolific developers gives interesting contrast to dogmas such as "functions/files should never be above x lines", where `quickjs.c` is 50k lines and has functions that are hundreds of lines long:

https://github.com/bellard/quickjs/blob/master/quickjs.c

(Obviously different approaches suites different circumstances.)

And some lightweight alternatives like Bellard's QuickJS (https://bellard.org/quickjs/) in C and Kiesel (https://kiesel.dev/) in Zig.

Built on a highly optimized JavaScript runtime powered by QuickJS, Query offers fast startup times and efficient execution. Its built-in caching mechanism further enhances performance by storing function responses, reducing database load and latency. This focus on speed makes Query a standout choice for server-side rendering, especially in applications with many components.

Where the previous SDK was built on top of the QuickJS JavaScript engine and the Javy runtime, the new SDK is built on top of the Firefox browser’s SpiderMonkey engine, and the Bytecode Alliance’s StarlingMonkey runtime and ComponentizeJS WIT bindings generator.

I'm currently using Bellard's QuickJS engine on a new TypeScript project.

Django MVC done right (and battle-tested)

Django

Django, for example, has a template engine that allows you to define a template in HTML and render it with a context -- data usually sourced from the database via the Django view. However, with its filters and helpers, it is almost too powerful -- undermining the core idea of templating. The same goes for Ember.js, as well.

I am maintaining a Python codebase that is based on Django and Django REST Framework (DRF). The codebase uses Nix for development, testing, CI/CD and packaging.

In the world of Python web development, Django is considered a powerhouse. It is one of the oldest, yet most actively developed web frameworks with a vibrant developer community. Technically speaking, Django is a third-party Python framework for creating web applications that run on a server.

Speed of Development: Frameworks such as Django or Rails accelerate the development process.

This ecosystem is fueled by repositories hosting powerful languages, functions, and versatile tools—from backend frameworks like Django and Ruby on Rails to containerization with Docker and distributed version control via Git. Moreover, indie hackers can also utilize open source design tools (e.g. GIMP, Inkscape) and analytics platforms such as Matomo.

Django

For the API, I will use the Django framework and other supporting libraries.

Beego is often characterized as a comprehensive, or "full-stack", framework, drawing parallels to the well-established Django framework in the Python ecosystem. It is designed to facilitate the rapid development of enterprise-grade applications and RESTful APIs by providing a wealth of built-in features.