Hacker News Reader

Hacker News

Comment by shivekkhurana | Hacker News Reader

Full thread

shivekkhurana

Not a framework but I'm tinkering with the following stack:

1. Hasura - DB + Basic APIS

2. Ory.sh for Auth/Authz

3. React on the frontend

4. Windmill.dev for Scheduling/Batch processing/ Background tasks

5. Docker for deployment

6. Fastify + Node JS for glue code (can use Windmill for Glue code too)

I have used Hasura extensively at 2 companies. It's well done and saves a ton of time.

You might also want to look at Retool (and its open-source alternatives). Web dev has become simpler now.

----

If you like code-focused solution: Rails, Laravel and Django are good options.

View on HN

I am loving Hasura so far. However, I am getting stuck with how to best write custom logic on top of this. For example: I have a products table, which Hasura will automatically generate schema for. But now I want to do a custom getProducts GraphQL query to do more advanced filtering (search, sort, ranking etc). What I end up doing it to have a remote schema. And now my clients need to understand two different product types (one generated by Hasura, and one generated by my custom remote schema. Do you have any advice on how to best resolve this?

On top of that, do you typically parse these Hasura Apollo into your client models? Or do you use the fragments directly in UI code since it already support types.

Hm…ideally your remote schema can return one or more product ids and then you can create a relationship back to the model from Postgres.

Link to docs: https://hasura.io/docs/latest/remote-schemas/remote-relation...

> 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.

Wohah, did not know about elm-graphql! I'm a big fan of functional programming and have written minor projects in elm, but the "slowness" of development has always discouraged me from actually doing something big with it. This stack might make this a whole lot better. Will look into it. Thanks

I tried it and it is INSANE how you can just focus on the UX/features and not have to worry about the boilerplate.

This is not just FP, this is "no runtime errors possible" FP.

With Elm-GraphQL your QUERY BUILDER is even fully type safe!

Robust productivity for the masses.

Are any of your Hasura apis used for public APIs? For internal only APIs, hasura is great. But I wanted to craft a public api with a particular schema, but that leads to difficulties because it’s all database driven. It reveals too much internal workings.

Reply on news.ycombinator.com