serverless-graphql | serverless app using Node.js , AWS Lambda | Runtime Evironment library
kandi X-RAY | serverless-graphql Summary
kandi X-RAY | serverless-graphql Summary
A Serverless Jukebox app built using AWS Lambda, React, GraphQL, API Gateway and Node.js. You can search for songs using the Last.fm api and save the names of songs you like to a playlist.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of serverless-graphql
serverless-graphql Key Features
serverless-graphql Examples and Code Snippets
Community Discussions
Trending Discussions on serverless-graphql
QUESTION
I am introducing my self to serverless and stumbled upon this: https://github.com/serverless-components/express and can't seem to understand what's difference with serverfull deployed to heroku? see i have this code in serverless:
...ANSWER
Answered 2021-Jan-21 at 19:22Some 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://www.serverless.com/blog/running-scalable-reliable-graphql-endpoint-with-serverless
https://aws.amazon.com/serverless/
https://serverless.com/blog/serverless-architecture-code-patterns/
QUESTION
There is this great repository with example implementations of different serverless scenarios.
Right now I'm struggling with the combination of AppSync and Amazon RDS. I tried the implementation of the standalone rds, and the appsync examples provided in the repository. These are working like a charm. But obviously there are many differences and difficulties if you'd like to combine these technologies. I used the schema, resolver and handler functions from the rds directory and combined it with the appsync lambda implementation. I adjusted the mapping templates and updated the serverless.yml file.
I could successfully deploy the whole appsync service and all resources without any errors. I'm able to access the graphql endpoint from graphiql and do my queries. But when I try it from the appsync console I get null as a response. I guess it has something to do with the mapping templates, but I'm not quite sure.
Has anybody got any suggestions or maybe a working example of this specific combination?
...ANSWER
Answered 2018-Jul-17 at 13:54I finally could figure out a working implementation for this specific setup which I want to share with all of you. Check out my serverless-graphql-appsync-rds repository on GitHub and leave me some feedback! Note that this repository contains just the source code without any explanations. I'll create a better documentation in the near future.
QUESTION
Ok, I'm on this problem since a few days.
I try to take this tutorial : https://serverless.com/blog/make-serverless-graphql-api-using-lambda-dynamodb/
And make it work with apollo-server-lambda. This tutorial help:
https://medium.com/vessels/apollo-server-serverless-graphql-bliss-68e8e15195ac
The problem is that nothing is working (for me) when you tried to use apollo server lambda with a real connection with DynamoDB. I got a list of errors that i can't remember anymore, it's just discouraging.
Here my code :
...ANSWER
Answered 2018-Jul-08 at 17:35Ok I figured out the problem. When you use the put function, you can't get the new item that you just insert in dynamoDB. You have to put "ReturnValues: 'ALL_OLD'" in your params object (first argument of the put function), like that no error is thrown, and you supposed to return the values you want since you just entered them in the db.
More details here:
QUESTION
Here's a reference setup of AWS Lambda and Serverless and GraphQL that i'm following:
https://github.com/serverless/serverless-graphql-apollo
I'm trying with yarn run start-server-lambda:offline
to start the project offline, it does start without any problems, but upon navigating to /graphiql
, I get this:
ANSWER
Answered 2017-Sep-28 at 16:23There's a configuration problem somewhere.
Basically, it's sending a request to /production/graphql
when it should have been sending it to /graphql
.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install serverless-graphql
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page