scotty VS Hasura

I would suggest checking out scotty for the http server - it uses warp by default, and is very beginner-friendly.

Here's the current commit I'm working with: https://github.com/scotty-web/scotty/commit/3ed8586c046b46dc42740e8ac2e7fe712e84191d

If you're not a fan of the ruby-on-rails / swiss army knife approach that IHP takes, check out Scotty. Add Lucid for Html rendering, and Selda for Postgres. (There are other options for any of these tools if you prefer)

- Scotty (simple web routing) https://hackage.haskell.org/package/scotty

Writing a Haskell webserver (maybe using scotty) and call it from node.

I've been looking for this as well, and found the globalstate.hs example in the scotty github repository. It uses a ReaderT of a TVar and shows how to update or read shared state in memory.

I've found htmx and hyperscript talking to scotty to be an easy way to get something like this going while retaining the joys of Haskell on the backend and avoiding the pains of Haskell on the frontend.

Finally, to add my opinion in the context of some other posts: I'd suggest Scotty (and probably other libraries I'm less familiar with) before Servant in particular, as Servant is a lot to absorb if you're also trying to build fluency in Haskell at the same time. Similarly, I'd advocate for Elmish (disclaimer, it's written by (very talented programmers other than myself at) my company) over Halogen, at least based on the last time I tried Halogen--I found it pretty complex as well. Don't get me wrong, I think Servant and Halogen are both great, just...complex.

This is an example of REST API built with Scotty a web framework of Haskell and PostgreSQL a relational database. It's a simple API to manage products.

Not that I'm much of an expert, but if you're talking about a very barebones static single-page-app, then you could very easily get by just using blaze-html to put your elements on the page, and then scotty is a basic web framework you could use to serve up your app.

> 2. ORMs do not hide SQL nastiness.

This is certainly true!

I mean: ORMs are now well known to "make the easy queries slightly more easy, while making intermediate queries really hard and complex queries impossible".

I think the are of ORMs is over. It simply did not deliver.

If a book on SQL is --say-- 100 pages, a book on Hibernate is 400 pages. So much to learn just to make the easy queries slightly easier to type? Just not worth it.

I prefer jooq any day over ORMs. And dont get me started over what tools like Hasuna have to offer.

There are also some languages (forgot the names) that are SQL-done-right. Select in the back, more type safe, more logic, more in the same steps as the query gets executed. These need to be adopted by PG and MySQL and we're good to go. (IMHO)

https://www.jooq.org/

https://hasura.io/

[4] https://github.com/hasura/graphql-engine/blob/master/architecture/live-queries.md

Another strategy is to model access control declaratively and enforce it in the application layer. ZenStack (built above Prisma ORM) and Hasura are good examples of this approach. The following code shows how access policies are defined with ZenStack and how a secured CRUD API can be derived automatically.

Today, this ecosystem is going strong with new providers like Hasura, AppWrite and Supabase powering millions of projects. There are a few reasons people choose this style of hosting, especially if they are more comfortable with frontend development. BaaS lets them set up a database in a secure way, expose some business logic on top of the data, and connect via a dev-friendly SDK from their app or website code to save data easily. These modern tools build a blend of managed database with curated plugins such as authentication, great admin dashboards, and function as a service type capability - all in one package, and often offered as a integrated hosted service.

Hi! If you’ve ever thought about something like using GraphQL for something like this.. You might like Hasura. (Obligatory I work for Hasura)

We’ve got an OpenAPI import and you can setup cron-jobs or one-off jobs and do things like load in headers from the environment variables to pass through. There isn’t currently an easy journey for chaining multiple calls together without writing any code at all, but you can wrap pretty much any API endpoint via OpenAPI import or a custom action, and you can even make minor edits to things like the API contract format to change aliases/naming.

Our goal is to join all the things, databases and API’s. Most people know us for instant GraphQL API’s that give you CRUD on your database, but we also wrap APIs.

Not sure if something like this would fit your use-case and do check out some of the other things mentioned, but depending what you are trying to do I think Hasura might potentially work.

You can find out more here: https://hasura.io

Nested Mutation - 113 thumbs up, and still open since 2019... another case of not listening to the users?

Hasura is an open-source real-time GraphQL API server with a strong authorization layer on your database. You can subscribe to database events via webhooks. It can combine multiple API servers into one unified graphQL API. Hasura is a great tool to build any CRUD GraphQL API. Hasura does not have any authentication mechanisms; e.g., you need an auth server to handle sign-up and sign-in.