We are using GraphQL for everything and are using AWS AppSync

Not your API but an API for Workers to talk to the database. There are limits and Workers is not a full node.js environment it’s a Node Isolates environment so you have to develop differently and many features are limited.

We don't call our AWS RDS Postgres databases directly and GraphQL handles everything including database calls

Everything goes through GraphQL first

Would this work?

If you are querying a GraphQL API endpoint from Workers it will work just fine. Basically you can't easily connect directly to a "traditional" database.

This makes a lot of sense

Basically everything that is HTTP(S) works without issues unless you bump into the subrequest limit (which I'm not sure if it increases in Unbound, @User).

Okay so that solves that. Now what about running our Node code?

Yeah there aren’t any plans to bump the subrequest limit that I’m aware of. Part of the reason that’s there is so no one can use Workers to DDoS

That depends on what you are doing and if that is supported in a Service Worker type of environment. There are certain limitations... https://developers.cloudflare.com/workers/runtime-apis

Yeah, gotcha. I can understand that...

Would be cool if subrequests to endpoints served with a domain specific CF cert could have a higher limit. That way I can't DDoS any random endpoint

@albert-zhao Whats the request limit?

The subrequest limit is 50 per request

I would imagine we would hit that very quickly

Ah interesting, how come that would be the case?

I don’t know if Workers supports GraphQL. I’ll look into this for you. If you’re calling an external API the answer is probably yes.

Depends on what features of node you use.

I believe it does because I saw an article from @kristian

Ah cool, I’ve only worked with REST not GraphQL, for my APIs but I’ve heard good things about it and want to learn it soon.

AWS AppSync makes it super easy!

We're looking into early next year at Node module support - will probably start with a subset of common Node APIs, such as HTTP, Crypto, and Buffer. Historically our engineers focused on Browser APIs because of their long-term compatibility. For Node, we may need to ask users what version they need us to be compatible with. For database support, like Postgres, it's a longer project with no timeline because we'll need to work with other teams to enable Workers for TCP.

It sounds like database support won't be an issue for us as we go through GraphQL and don't call the database directly

@Gary Somerhalder Check out this article which explains how Workers and Node Isolates works if you find time https://developers.cloudflare.com/workers/learning/how-workers-works

In the meantime, we're working on tutorials for connecting to databases that we can do today, like Google Firestore, AWS Aurora Serverless, and others that connect via HTTP. 🙂

I would be very interested in this as we have 5 companies that could all use Workers then

This is very cool!

We have been looking into AWS Aurora Serverless running Postgres