django_for_startups
fquery
| django_for_startups | fquery | |
|---|---|---|
| 2 | 5 | |
| 137 | 10 | |
| - | - | |
| 0.0 | 0.0 | |
| about 1 year ago | over 2 years ago | |
| Python | Python | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
django_for_startups
-
Django 4.0 Released
> function based views
Class-based views, in their most basic form, are a lot easier to read. E.g. look at the DRF CBVs I have here:
https://github.com/Alex3917/django_for_startups/blob/main/dj...
If you can avoid Generic CBVs (things like ListView) and inheritance, then the only difference between FBVs and CBVs is that CBVs make it easier to see what's a GET / PUT / POST / DELETE.
-
Django for Startup Founders: A better software architecture for SaaS startups
No, but all the code for the book is on GitHub: https://github.com/Alex3917/django_for_startups
fquery
-
Solving the double (quintuple) declaration Problem in GraphQL Applications
Similar benefits without codegen (based on decorator magic) for a python based stack:
https://github.com/adsharma/fquery
* Use dataclasses for both database schema and the user facing operations
- Cut Out the Middle Tier: Generating JSON Directly from Postgres
- Against SQL
- Django for Startup Founders: A better software architecture for SaaS startups
-
SwiftGraphQL – A GraphQL client that lets you forget about GraphQL
Re: Conways law at Facebook
I was at Facebook when GraphQL was invented, maintaining a backend storage service where a core assumption was that storage should be reorganized based on access patterns and that predicates should be pushed down to storage where they can be executed more efficiently.
GraphQL was hard to push predicates down, because you don't know which of the edges were written in PHP.
My response was fquery[1], which is like what's being discussed here but with python as the source language instead of swift and amenable to preserving the largest possible query structure for backend optimizers, including SQL optimizers.
It has some early demos converting a GraphQL/fquery into SQL where possible. It should be possible to add enough metadata to fquery to identify if an edge is non-trivial (calls into another microservice) or trivial (can be optimized to a storage backend or SQL).
[1] https://github.com/adsharma/fquery
What are some alternatives?
django-ninja - 💨 Fast, Async-ready, Openapi, type hints based framework for building APIs
django-zen-queries - Explicit control over database query execution in Django applications
rel8 - Hey! Hey! Can u rel8?
re-frame - A ClojureScript framework for building user interfaces, leveraging React
prosto - Prosto is a data processing toolkit radically changing how data is processed by heavily relying on functions and operations with functions - an alternative to map-reduce and join-groupby
django-extensions - This is a repository for collecting global custom management extensions for the Django Framework.
DjangoChannelsGraphqlWs - Django Channels based WebSocket GraphQL server with Graphene-like subscriptions
Poetry - Python packaging and dependency management made easy
jrutil
fastapi - FastAPI framework, high performance, easy to learn, fast to code, ready for production
htmx - </> htmx - high power tools for HTML