nhost VS apollo-server

Hasura ❌ (technically yes with Nhost)

Only caveat I say is make sure there's something in it for you; if it's 2 AM it better be mostly for self-benefit. I'm busy constructing a monorepo with the latest technology with NX and pnpm and a half dozen other technologies (I recommend checking out http://nhost.io/); at the end I will build whatever I want and maybe make money. It's not done for the good of someone else exclusively that's for sure

Yeah, I knew of those, I think that's discussed often enough on the dotnet subs. Ory and Zitadel I knew too, but those provide just one thing, and are not native to dotnet. Altough I'll admit, stuff like nhost seem native to typescript but uses go projects under the covers as well.

I'm really digging nhost and apollo-client.

You can use Nhost (100% open source): https://github.com/nhost/nhost/tree/main/examples/docker-compose

Backend Frontend Database pick two or even one. Maybe something like this

I am trying to use basic authentication of nhost.io .

If your backend needs aren't super crazy, i would check out https://nhost.io/

Another interesting point is that executing fetches on the server can allow developers to more easily leverage caching. Next.js already handles caching out-of-the-box and I’m curious to see if the wider adoption of RSC reduces the need to combine React with solutions like Apollo Server and Apollo Client. While there are other benefits to these tools, RSC could provide similar caching behavior without the need to invest in a GraphQL solution.

There are several GraphQL server implementations, however, for this tutorial, we'll utilize Apollo GraphQL's Apollo Server, a lightweight and flexible JavaScript server that makes it easy to build GraphQL APIs.

As I mentioned, their main GraphQL server package is[1], so that's where the confusion came from. Thanks.

[1] https://github.com/apollographql/apollo-server/blob/9817bc47...

While working on this blog post, I learned that Apollo Server, the most popular GraphQL server for typescript, uses a similar method for adding error codes to GraphQL. It even lets you add custom errors. Hopefully, someday other GraphQL server projects will follow them. Until then, we’ve got a strong indication we took the right approach.

GraphQL is just a schema, there are many different implementations of a GraphQL server, AppSync being one of them. I mentioned Apollo server in this series as well.

After some head-scratching, I opened an issue on Apollo Server’s GitHub repository. There, Apollo Server contributor @​glasser shared a helpful suggestion: why not invoke our AuthPlugin from Apollo Server’s context function? Throwing from context would ensure we can control the HTTP status response without having to introduce more methods and error checks to our AuthPlugin (like unexpectedErrorProcessingRequest). With that suggestion in mind, we rewrote our AuthPlugin as follows:

Apollo as a middleware in Express.js, actually.

Apollo Server 3 Cookie Issue #5775

Lastly, instead of writing our API core ourselves, we'll be using the star of this episode --- Apollo Server (a.k.a. GraphQL server). It has detailed documentation available here.