amplify-flutter VS graphql-subscriptions

AWS Amplify - Build apps with cloud features by Amazon Web Services

Together these updates speed up building fullstack applications on AWS. We’d love to hear your feedback as you build! To learn more, visit our docs site!

In this blog post we’ve learned about Amplify Studio forms, how to customize them and how to add additional validation error messages. If you’d like to learn more about Amplify in general please check out the official docs. You can also check the Amplify Studio tutorial for more information on how to use it.

You might find it easier using AWS Amplify https://docs.amplify.aws/

We do not have support for Geo queries, please upvote this Github issue https://github.com/aws-amplify/amplify-flutter/issues/2495,

Deploying a Next.js application can be a daunting task for developers if you are not using Vercel. But with Amazon Amplify, you can easily and quickly deploy your app without sacrificing key functionalities such as ISR, SSR, and other Next.js goodies.

If you're looking to learn more about Amplify, head to our docs and join our Discord community.

Amplify, on the other hand, is a set of tools that allows full-stack web and mobile developers the ability to create and build apps using AWS services.

Amplify is a set of tools that allows full-stack web and mobile developers to create and build apps. It makes using AWS services, like our Cognito identity and access management service, or our managed GraphQL service AppSync, much simpler and straight forward to use.

Hello, thank you for your comment! It is in our radar, we will do our best to bring support for Amplify Push Notifications as soon as we can. You can check the GitHub issue for further updates --> https://github.com/aws-amplify/amplify-flutter/issues/319

graphql-yoga is built on other packages that provide functionality required for building a GraphQL server such as web server frameworks like express and apollo-server, GraphQL subscriptions with graphql-subscriptions and subscriptions-transport-ws, GraphQL engine & schema helpers including graphql.js and graphql-tools, and an interactive GraphQL IDE with graphql-playground.

The most common used (but not best maintained) library for such a PubSub engine in the GraphQL context is graphql-subscriptions. There are also adapters available for more distributed systems (where all GraphQL API replicas must be notified about the event) e.g. over Redis.

During that work, we created and merged the reference implementation into graphql-js and created two supporting libraries: graphql-subscriptions and subscriptions-transport-ws. Here is a talk with deep dive into all the details.

The Prisma / GraphQL-Yoga comes with Subscriptions, and this was the first thing I came across when my client asked for realtime updates. The implementation was quite difficult - took me a long time. Eventually, it was working locally, and in staging. However, when it came to the production environment, for some reason it just didn't work! This unfortunately ended up with a user losing an auction, which ultimately went to court etc.

There are also other solutions available: https://github.com/apollographql/graphql-subscriptions#pubsub-implementations

First, let's try to understand what PubSub is exactly. Apollo Server uses a publish-subscribe (pub/sub) model to track events that update subscriptions. The graphql-subscriptions library included in all apollo-server packages (including middleware integrations) provides a PubSub class as a basic in-memory event bus.

To add this, I can just expand the basic setup above. To do so, I do actually use a couple of small Apollo modules! Most can be picked and configured independently. For this case, graphql-subscriptions provides a little bit of pubsub logic that works within resolvers, and subscriptions-transport-ws integrates that into Express to handle the websockets themselves. Super helpful