low-code-backend-dockered
fquery
Our great sponsors
low-code-backend-dockered | fquery | |
---|---|---|
9 | 5 | |
43 | 10 | |
- | - | |
0.0 | 0.0 | |
about 2 years ago | over 2 years ago | |
JavaScript | Python | |
- | 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.
low-code-backend-dockered
-
Ask HN: Hunting for a Framework
> 1. Hasura - DB + Basic APIS, 2. Ory.sh for Auth/Authz
Great choices!
3. React on the frontend
Here I'd go with Elm, and a generated GraphL API client. Here an example to play with (which btw also includes ZomboDB for ElasticSearch integration into Postgres)
https://github.com/cies/low-code-backend-dockered
> 4. Windmill.dev
Look awesome, never heard of it. Tnx
> If you like code-focused solution: Rails, Laravel and Django are good options.
I think Kotlin/KTor, while not as full featured, is a much better alternative due to the strong typing discipline.
-
A Love Letter to Ruby and Rails
I was a big Rails, Ruby and dynamic typing fanboy. But then my project grew in size and I changed my beliefs.
I'd not start a big project in any language without: null-safety, proper sum-types, type inference.
Hence I like Kotlin, and KTor seems to be a good Sinatra/Flask like in that arena.
Another interesting development I find no-code/low-code tools for the backend, like Hasura. This allows me to "just expose Postgres over GraphQL" with very little code (mainly configuration). That combined with type-safe client library generation for a typesafe frontend language like Elm gives me all the power I need in a very different paradigm. Something worth considering.
Small example Hasura+Elm project: https://github.com/cies/low-code-backend-dockered
- Best way to create web application?
-
Hasura Super App - A reference application for the real-world with Hasura, Next.js, and TypeScript
My plug: https://github.com/cies/elm-hasura-dockered
-
Django for Startup Founders: A better software architecture for SaaS startups
I agreed. Then did a project[1] with Hasura and a generated client lib in Elm and I'm no longer looking back. If I can get away with "no backend code" I'll do it again in a heart beat.
[1] https://github.com/cies/elm-hasura-dockered
- Show HN: Fully dockered, typesafe front end starter-kit with Elm and Hasura
- Demo of strong type safety with GraphQL using Elm and Hasura
- Fully dockered Elm-Hasura starter kit
- Fully dockered Elm-Hasura starter kit: strong typesafety from db schema to frontend code
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