graphql-api | opinionated Graphql framework for Rails that supports auto | GraphQL library

Edit 28/02/2022:

Support for .NET 6 runtime for AWS Lambda is available now: Introducing the .NET 6 runtime for AWS Lambda

Some recommendations from Amazon (full article):

To get started immediately with .NET 6 on Lambda there are some options:

• Managed base container image - Pull from the ECR Public Gallery or use .NET 6 container image Blueprint in the AWS Toolkit for Visual Studio.
• Custom container image - Build a container image with the .NET 6 application packaged inside it. This PowerShell script will build a .NET 6 base container image.
• Custom runtime - The custom runtime bundles all necessary .NET 6 libraries in the zip file archive that is deployed to Lambda, see this example. For an ARM64 see this example.

Managed instances with .NET 6 should be available in the near future.

If you read my question carefully, you will find several clues pointing to a concurrency problem.

threads_count = 2

If the frontend requests multiple requests at a time, not all requests are processed properly

If I set the thread_count to 1, there's no error

At the time, I didn't see those clues and didn't know what was going on ;). Often you can't see the forest for the trees.

@Myst could see the clues and pointed me in the right direction.

I'm using great hanami-api for my API and the controllers are hanami-controllers (1.3). Here's a code-snippet, which includes the concurrency-bug:

Can you check if there is a resolver attached to your (failing) Appsync API ?

If you have access to the web console look for this screen:

If there is nothing attached to getTable then that's probably why you are having null answers. Resolvers Docs

Not sure amplify docs is the best one to use for learning Lambda. Second, why do you want to use GraphQL to perform CRUD operations on an Amazon DynamoDB table from within a Lambda function. There are other ways such as using the JavaScript SDK from within a Lambda function as discussed here in the JavaScript Developer Guide:

Creating scheduled events to execute AWS Lambda functions

Looks like graphql-moment code isn't being published with a commonJS, UMD, or some other compatible format and Jest can't parse it. What you're most likely going to need to do is either mock it in your tests like so:

Let's break this down a little, because you may have accidentally asked a lot of questions that aren't easily answered in a short single paragraph :)

First of all, what makes a REST API?

REST API's use a subset of HTTP methods and the protocol itself to transfer API data and transmit changes to an API. In other words, it's a client-server protocol which operates using the parameters of an endpoint, a method, the headers, and a body and/or query parameters. It's constrained to be stateless, meaning that we must be able to send any call at any time, simply speaking.

We have several HTTP methods in use to get data, update data, create data, and delete data. However, there's no strict standard beyond this that's enforced to define how these endpoints are structured or how they behave. There are some loose rules however.

It's common to compare REST to GraphQL, however, this comparison isn't always going to make sense, as we're just comparing two approaches (out of many) to create APIs, but aren't comparing apples to apples. GraphQL is a specification that creates a new form of typed, stateless, relational API which is more akin to REST together with JSON schemas and Swagger.

But, what about GraphQL?

GraphQL over HTTP is actually seemingly comparable to REST APIs, but in actuality it's just GraphQL queries being executed against a GraphQL schema that happens to be accessible via an HTTP endpoint. It's however not restricted to HTTP. This is where we can start to see the differences. REST may also be an approach, but it's become a common method to build out an HTTP API. GraphQL is a schema language, query language, and API system that isn't strictly speaking constrained to HTTP. Hence, it can't be REST-compliant. (However, do look into "Persisted Queries" and "Automatic Persisted Queries" to see how we can still use HTTP CDNs)

The closest approximation to a GraphQL over HTTP API is actually not REST, surprisingly. It's SOAP APIs, aka the Simple Objects Access Protocol from 1998. That's because SOAP also focuses on exchanging structured information.

GraphQL is very advantageous at modelling relational data and giving us an API that can freely be constructed to access relational nodes. It defines a schema language that defines the types and other constraints of the executable schema (which is also separated into modify/query, so not dissimilar to REST methods), and a query language using which we can traverse this schema graph.

Lastly, asking for an alternative here is hard. A lot of time has gone into GraphQL, and while I'm aware of some smaller alternatives, none are as popular. It's important here to note that GraphQL is just a specification, when you take everything else away. Hence, it isn't important to find "alternatives" because there are several implementations of it and it builds an ecosystem. In other words, it's adopted beyond just Facebook and this wide adoption helps community tooling.

Assuming a standard setup, the following can be added to configureExpress (see here) to apply Keystone session middleware to a custom express endpoint:

Some of the benefits of serverless: you execute your code on-demand only when it's needed in contrast to the traditional servers that will be running 24/7. In addition, it also managed by a service provider so you won't need to worry about maintaining and scaling your server.

You can read more

https://dashbird.io/blog/business-benefits-of-serverless/#:~:text=A%20company%20that%20can%20draw,will%20improve%20the%20user%20experience.

https://www.serverless.com/blog/running-scalable-reliable-graphql-endpoint-with-serverless

https://aws.amazon.com/serverless/

https://serverless.com/blog/serverless-architecture-code-patterns/