Im using AWS AppSync in my react native application. I followed many tutorials , this in particular : https://docs.aws.amazon.com/appsync/latest/devguide/building-a-client-app-reactnative.html
In this tutorial, provided by AWS, they use Apollo Graphql : «
AWS AppSync integrates with the Apollo GraphQL client for building client applications. AWS provides Apollo plugins for offline support, authorization, and subscription handshaking. You can use the Apollo client directly, or you can use it with some of the client helpers provided in the AWS AppSync SDK. »
But, with the new release of the AWS AppSync documentation, we get another way to work.
So my question is : What is the best way to use GraphQL with AWS AppSync?
Why there is no information about Apollo GraphQL in the documentation while it uses in the tutorial?
Thanks you in advance for your answers/advices.
Related
I am working with an API that doesn't have introspection enabled from the back end.
The only thing I have is a curl command to access the API. How do I access it in Kotlin using Apollo?
I've just one question, can I make separate server app (backend) with GraphQL API for my Next.JS app (frontend)? I clearly understand technical part of such implementation, but what about supporting Next.JS advantages (for example ability of deploying on Vercel)?
In my opinion, this approach will support all things which available for normal Next.JS app with API Routes (api/graphql), I just make my own API (like very very small GraphCMS), but may be I missed something.
Thanks in advance for all your opinions!
I am using Apollo Server v2.0 (without middleware) as part of my project and I would like to add support for a HTTP GET endpoint to for file downloads. Is there a way to expose an API endpoint without using apollo-server-express?
Thank you
No. While apollo-server currently uses express under the hood, the Express instance is not exposed as a property on the ApolloServer instance. In order to expose any additional endpoints, you'd need to migrate to apollo-server-express or any of the other available framework integrations. The migration is relatively painless since the APIs are almost identical.
I created a RAML file in API Design, then deployed in API manager and implemented in API runtime manager. It is clear no issues now.
Now i got change in raml file. I did changes in API Design and published into exchange with v2.
The problem here is how to import the v2 API into API manager ?
after importing the new api do i need to add all policies applied on v1 API to v2 API again ?
or is there any automatic option ?
I don't find any options in API manager, please help me..,
Yes, we need to apply policies again. Even when there is the same API version have 2 instances.
If you do not have major change then you can just go to action and upgrade to next assent version of the same API. Else you need to apply policies.
Ranveer
I have a question about deployment strategy with vue.js + express.js + lambda.
I can deploy express.js to lambda with serverless as backend. and then where can I deploy vue.js as frontend? I saw some kind of article. They deployed S3 and domain forward to S3 bucket. Is this common way?
I mean If I make html file in express.js and deploy to lambda. that's just one shot deployment. Can I deploy like this with vue.js?
thanks for answering in advance.
You can deploy your frontend (be it in Vue, React, Angular) via S3 by Hosting a Static Website using Amazon S3
Your frontend can then invoke API Gateway which will trigger your Lambda functions (which happens to be the backend of your application)