| fquery | rel8 | |
|---|---|---|
| 5 | 5 | |
| 10 | 156 | |
| - | 0.0% | |
| 7.0 | 6.8 | |
| 3 days ago | about 1 month ago | |
| Python | Haskell | |
| MIT License | GNU General Public License v3.0 or later |
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.
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
rel8
-
Choosing the right abstraction level for SQLite library.
I also mention https://github.com/circuithub/rel8 on posts like these since I think it should be more well-known.
-
What's your favorite Database EDSL/library in Haskell?
I'm sensing a trend here, but .... https://rel8.readthedocs.io/ because I wrote it ':D
-
[ANN] Generic-Persistence 0.3.0 released
Does this work with https://github.com/circuithub/rel8?
- Against SQL
- [video] Ollie Charles: Rel8, a new database access library for Haskell
What are some alternatives?
django-ninja - 💨 Fast, Async-ready, Openapi, type hints based framework for building APIs
opaleye
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
Preql - An interpreted relational query language that compiles to SQL.
DjangoChannelsGraphqlWs - Django Channels based WebSocket GraphQL server with Graphene-like subscriptions
cimple - Cimple and Apidsl language parsers and tools
jrutil
django_for_startups - Code for the book Django for Startups
PostgreSQL - Mirror of the official PostgreSQL GIT repository. Note that this is just a *mirror* - we don't work with pull requests on github. To contribute, please see https://wiki.postgresql.org/wiki/Submitting_a_Patch
django-channels - Developer-friendly asynchrony for Django
generic-persistence - GenericPersistence is a Haskell persistence library for relational databases. The approach relies on GHC.Generics. A real-world demo can be found here: