Alternatives to AWS AppSync logo

Alternatives to AWS AppSync

Prisma, Firebase, AWS Mobile Hub, AWS Amplify, and Realm are the most popular alternatives and competitors to AWS AppSync.
197
257
+ 1
30

What is AWS AppSync and what are its top alternatives?

AWS AppSync automatically updates the data in web and mobile applications in real time, and updates data for offline users as soon as they reconnect. AppSync makes it easy to build collaborative mobile and web applications that deliver responsive, collaborative user experiences.
AWS AppSync is a tool in the GraphQL as a Service category of a tech stack.

Top Alternatives to AWS AppSync

  • Prisma
    Prisma

    Prisma is an open-source database toolkit. It replaces traditional ORMs and makes database access easy with an auto-generated query builder for TypeScript & Node.js. ...

  • Firebase
    Firebase

    Firebase is a cloud service designed to power real-time, collaborative applications. Simply add the Firebase library to your application to gain access to a shared data structure; any changes you make to that data are automatically synchronized with the Firebase cloud and with other clients within milliseconds. ...

  • AWS Mobile Hub
    AWS Mobile Hub

    AWS Mobile Hub is the fastest way to build mobile apps powered by AWS. It lets you easily add and configure features for your apps, including user authentication, data storage, backend logic, push notifications, content delivery, and analytics. After you build your app, AWS Mobile Hub gives you easy access to testing on real devices, as well as analytics dashboards to track usage of your app – all from a single, integrated console. ...

  • AWS Amplify
    AWS Amplify

    A JavaScript library for frontend and mobile developers building cloud-enabled applications. The library is a declarative interface across different categories of operations in order to make common tasks easier to add into your application. The default implementation works with Amazon Web Services (AWS) resources but is designed to be open and pluggable for usage with other cloud services that wish to provide an implementation or custom backends. ...

  • Realm
    Realm

    The Realm Mobile Platform is a next-generation data layer for applications. Realm is reactive, concurrent, and lightweight, allowing you to work with live, native objects. ...

  • Firebase Realtime Database
    Firebase Realtime Database

    It is a cloud-hosted NoSQL database that lets you store and sync data between your users in realtime. Data is synced across all clients in realtime, and remains available when your app goes offline. ...

  • Apollo
    Apollo

    Build a universal GraphQL API on top of your existing REST APIs, so you can ship new application features fast without waiting on backend changes. ...

  • Hasura
    Hasura

    An open source GraphQL engine that deploys instant, realtime GraphQL APIs on any Postgres database. ...

AWS AppSync alternatives & related posts

Prisma logo

Prisma

1.1K
949
54
Modern Database Access for TypeScript & Node.js
1.1K
949
+ 1
54
PROS OF PRISMA
  • 12
    Type-safe database access
  • 10
    Open Source
  • 8
    Auto-generated query builder
  • 6
    Supports multible database systems
  • 6
    Increases confidence during development
  • 4
    Built specifically for Postgres and TypeScript
  • 4
    Productive application development
  • 2
    Supports multible RDBMSs
  • 2
    Robust migrations system
CONS OF PRISMA
  • 2
    Doesn't support downward/back migrations
  • 1
    Doesn't support JSONB
  • 1
    Do not support JSONB
  • 1
    Mutation of JSON is really confusing
  • 1
    Do not support JSONB

related Prisma posts

Divine Bawa
at PayHub Ghana Limited · | 16 upvotes · 484.6K views

I just finished a web app meant for a business that offers training programs for certain professional courses. I chose this stack to test out my skills in graphql and react. I used Node.js , GraphQL , MySQL for the #Backend utilizing Prisma as a database interface for MySQL to provide CRUD APIs and graphql-yoga as a server. For the #frontend I chose React, styled-components for styling, Next.js for routing and SSR and Apollo for data management. I really liked the outcome and I will definitely use this stack in future projects.

See more
Collins Ogbuzuru
Front-end dev at Evolve credit · | 15 upvotes · 27.2K views
Shared insights
on
GraphQLGraphQLPrismaPrismaAWS LambdaAWS Lambda

We are starting to build one shirt data logic, structure and as an online clothing store we believe good ux and ui is a goal to drive a lot of click through. The problem is, how do we fetch data and how do we abstract the gap between the Front-end devs and backend-devs as we are just two in the technical unit. We decided to go for GraphQL as our application-layer tool and Prisma for our database-layer abstracter.

Reasons :

GraphQL :

  1. GraphQL makes fetching of data less painful and organised.

  2. GraphQL gives you 100% assurance on data you getting back as opposed to the Rest design .

  3. GraphQL comes with a bunch of real-time functionality in form of. subscriptions and finally because we are using React (GraphQL is not React demanding, it's doesn't require a specific framework, language or tool, but it definitely makes react apps fly )

Prisma :

  1. Writing revolvers can be fun, but imagine writing revolvers nested deep down, curry braces flying around. This is sure a welcome note to bugs and as a small team we need to focus more on what that matters more. Prisma generates this necessary CRUD resolves, mutations and subscription out of the box.

  2. We don't really have much budget at the moment so we are going to run our logic in a scalable cheap and cost effective cloud environment. Oh! It's AWS Lambda and deploying our schema to Lambda is our best bet to minimize cost and same time scale.

We are still at development stage and I believe, working on this start up will increase my dev knowledge. Off for Lunch :)

See more
Firebase logo

Firebase

40.8K
35K
2K
The Realtime App Platform
40.8K
35K
+ 1
2K
PROS OF FIREBASE
  • 371
    Realtime backend made easy
  • 270
    Fast and responsive
  • 242
    Easy setup
  • 215
    Real-time
  • 191
    JSON
  • 134
    Free
  • 128
    Backed by google
  • 83
    Angular adaptor
  • 68
    Reliable
  • 36
    Great customer support
  • 32
    Great documentation
  • 25
    Real-time synchronization
  • 21
    Mobile friendly
  • 19
    Rapid prototyping
  • 14
    Great security
  • 12
    Automatic scaling
  • 11
    Freakingly awesome
  • 8
    Super fast development
  • 8
    Angularfire is an amazing addition!
  • 8
    Chat
  • 6
    Firebase hosting
  • 6
    Built in user auth/oauth
  • 6
    Awesome next-gen backend
  • 6
    Ios adaptor
  • 4
    Speed of light
  • 4
    Very easy to use
  • 3
    Great
  • 3
    It's made development super fast
  • 3
    Brilliant for startups
  • 2
    Free hosting
  • 2
    Cloud functions
  • 2
    JS Offline and Sync suport
  • 2
    Low battery consumption
  • 2
    .net
  • 2
    The concurrent updates create a great experience
  • 2
    Push notification
  • 2
    I can quickly create static web apps with no backend
  • 2
    Great all-round functionality
  • 2
    Free authentication solution
  • 1
    Easy Reactjs integration
  • 1
    Google's support
  • 1
    Free SSL
  • 1
    CDN & cache out of the box
  • 1
    Easy to use
  • 1
    Large
  • 1
    Faster workflow
  • 1
    Serverless
  • 1
    Good Free Limits
  • 1
    Simple and easy
CONS OF FIREBASE
  • 31
    Can become expensive
  • 16
    No open source, you depend on external company
  • 15
    Scalability is not infinite
  • 9
    Not Flexible Enough
  • 7
    Cant filter queries
  • 3
    Very unstable server
  • 3
    No Relational Data
  • 2
    Too many errors
  • 2
    No offline sync

related Firebase posts

Stephen Gheysens
Lead Solutions Engineer at Inscribe · | 14 upvotes · 1.8M views

Hi Otensia! I'd definitely recommend using the skills you've already got and building with JavaScript is a smart way to go these days. Most platform services have JavaScript/Node SDKs or NPM packages, many serverless platforms support Node in case you need to write any backend logic, and JavaScript is incredibly popular - meaning it will be easy to hire for, should you ever need to.

My advice would be "don't reinvent the wheel". If you already have a skill set that will work well to solve the problem at hand, and you don't need it for any other projects, don't spend the time jumping into a new language. If you're looking for an excuse to learn something new, it would be better to invest that time in learning a new platform/tool that compliments your knowledge of JavaScript. For this project, I might recommend using Netlify, Vercel, or Google Firebase to quickly and easily deploy your web app. If you need to add user authentication, there are great examples out there for Firebase Authentication, Auth0, or even Magic (a newcomer on the Auth scene, but very user friendly). All of these services work very well with a JavaScript-based application.

See more
Eugene Cheah

For inboxkitten.com, an opensource disposable email service;

We migrated our serverless workload from Cloud Functions for Firebase to CloudFlare workers, taking advantage of the lower cost and faster-performing edge computing of Cloudflare network. Made possible due to our extremely low CPU and RAM overhead of our serverless functions.

If I were to summarize the limitation of Cloudflare (as oppose to firebase/gcp functions), it would be ...

  1. <5ms CPU time limit
  2. Incompatible with express.js
  3. one script limitation per domain

Limitations our workload is able to conform with (YMMV)

For hosting of static files, we migrated from Firebase to CommonsHost

More details on the trade-off in between both serverless providers is in the article

See more
AWS Mobile Hub logo

AWS Mobile Hub

20
124
0
Build, test, and monitor usage of your mobile apps
20
124
+ 1
0
PROS OF AWS MOBILE HUB
    Be the first to leave a pro
    CONS OF AWS MOBILE HUB
      Be the first to leave a con

      related AWS Mobile Hub posts

      AWS Amplify logo

      AWS Amplify

      491
      548
      15
      JavaScript Open Source Library with React, React Native Extensions
      491
      548
      + 1
      15
      PROS OF AWS AMPLIFY
      • 5
        GraphQL
      • 3
        Better with Relations and Security
      • 2
        Flexible Auth options
      • 2
        Cheaper
      • 1
        Backed by Amazon
      • 1
        Config free environment variables
      • 1
        Continuous deployment
      • 0
        Jije
      CONS OF AWS AMPLIFY
      • 2
        Free tier is limited
      • 1
        Steep Learning Curve

      related AWS Amplify posts

      I am currently working on a long term mobile app project. Current stack: Frontend: Dart/Flutter Backend: Go, AWS Resources (AWS Lambda, Amazon DynamoDB, etc.) Since there are only two developers and we have limited time and resources, we are looking for a BAAS like Firebase or AWS Amplify to handle auth and push notifications for now. We are prioritizing developing speed so we can iterate quickly. The only problem is that AWS amplify support for flutter is in developer preview and has limited capabilities (We have tested it out in our app). Firebase is the more mature option. It has great support for flutter and has more than we need for auth, notifications, etc. My question is that, if we choose firebase, we would be stuck with using two different cloud providers. Is this bad, or is this even a problem? I am willing to change anything on the backend architecture wise, so any suggestions would be greatly appreciated as I am somewhat unfamiliar with Google Cloud Platform. Thank you.

      See more

      I am now building a React Native app, and I don't know what to choose for my backend between AWS Amplify and Firebase. Which one fits more with react native?

      See more
      Realm logo

      Realm

      268
      439
      16
      Realm makes it easy to build reactive apps, realtime collaborative features, and offline-first experiences.
      268
      439
      + 1
      16
      PROS OF REALM
      • 7
        Good
      • 3
        Elegant API
      • 3
        Cloud Syncing
      • 2
        React Native Support
      • 1
        Strong Adoption Growth
      CONS OF REALM
      • 1
        No offline support for web till now

      related Realm posts

      Mike Endale
      Shared insights
      on
      Android SDKAndroid SDKRealmRealmPouchdbPouchdb
      at

      We are building an offline-first Android SDK app. The solution we're working on runs on a mobile device in areas where internet connectivity is intermittent or does not exist. The applications needs to be able to collect data and when it reaches a home base or finds internet connectivity, we'll sync it with the host.

      We've heard Realm and Pouchdb could be a good solution, but we are curious if anyone has any experience with either or have another path forward.

      See more
      Gabriel Pa

      If you want to use Pouchdb might as well use RxDB which is an observables wrapper for Pouch but much more comfortable to use. Realm is awesome but Pouchdb and RxDB give you more control. You can use Couchbase (recommended) or CouchDB to enable 2-way sync

      See more
      Firebase Realtime Database logo

      Firebase Realtime Database

      108
      229
      7
      Store and sync data in real time
      108
      229
      + 1
      7
      PROS OF FIREBASE REALTIME DATABASE
      • 7
        Very fast
      • 0
        Casandra
      CONS OF FIREBASE REALTIME DATABASE
      • 2
        Poor query

      related Firebase Realtime Database posts

      We are building a social media app, where users will post images, like their post, and make friends based on their interest. We are currently using Cloud Firestore and Firebase Realtime Database. We are looking for another database like Amazon DynamoDB; how much this decision can be efficient in terms of pricing and overhead?

      See more

      Which option do you prefer to go with (considering scalability, and a limited budget):

      Technologies in use: Angular / .NET Core 6

      What do we want to achieve?

      We want to create simple near-time web notifications, those notifications can be categorized into 2 sections:

      • User notification: which represents user activities and engagements.

      • System notification e.g release notes and maintenance time. The notification object is too simple just a title, body, userId, notificationStatus, and readAt. notification status is an enum with 3 values: unread, menuOpened, Read.

      Options:

      1. use Firebase Realtime Database for user notifications and Microsoft SQL Server for system notifications (maybe using long poling or so to frequently call the getSystemNotification API ).

      2. use SignalR to push new notifications along with the SqlServer database and store both user and system into one table (as they almost have the same attributes)

      See more
      Apollo logo

      Apollo

      2.4K
      1.8K
      25
      GraphQL server for Express, Connect, Hapi, Koa and more
      2.4K
      1.8K
      + 1
      25
      PROS OF APOLLO
      • 12
        From the creators of Meteor
      • 8
        Great documentation
      • 3
        Open source
      • 2
        Real time if use subscription
      CONS OF APOLLO
      • 1
        File upload is not supported
      • 1
        Increase in complexity of implementing (subscription)

      related Apollo posts

      Nick Rockwell
      SVP, Engineering at Fastly · | 46 upvotes · 3.9M views

      When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

      So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

      React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

      Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

      See more
      Adam Neary

      At Airbnb we use GraphQL Unions for a "Backend-Driven UI." We have built a system where a very dynamic page is constructed based on a query that will return an array of some set of possible “sections.” These sections are responsive and define the UI completely.

      The central file that manages this would be a generated file. Since the list of possible sections is quite large (~50 sections today for Search), it also presumes we have a sane mechanism for lazy-loading components with server rendering, which is a topic for another post. Suffice it to say, we do not need to package all possible sections in a massive bundle to account for everything up front.

      Each section component defines its own query fragment, colocated with the section’s component code. This is the general idea of Backend-Driven UI at Airbnb. It’s used in a number of places, including Search, Trip Planner, Host tools, and various landing pages. We use this as our starting point, and then in the demo show how to (1) make and update to an existing section, and (2) add a new section.

      While building your product, you want to be able to explore your schema, discovering field names and testing out potential queries on live development data. We achieve that today with GraphQL Playground, the work of our friends at #Prisma. The tools come standard with Apollo Server.

      #BackendDrivenUI

      See more
      Hasura logo

      Hasura

      332
      629
      144
      An open source GraphQL engine that deploys instant, realtime GraphQL APIs on any Postgres database.
      332
      629
      + 1
      144
      PROS OF HASURA
      • 23
        Fast
      • 18
        Easy GraphQL subscriptions
      • 16
        Easy setup of relationships and permissions
      • 15
        Automatically generates your GraphQL schema
      • 15
        Minimal learning curve
      • 13
        No back-end code required
      • 13
        Works with new and existing databases
      • 12
        Instant production ready GraphQL
      • 11
        Great UX
      • 4
        Low usage of resources
      • 4
        Simple
      CONS OF HASURA
      • 3
        Cumbersome validations

      related Hasura posts