nodejs-storage VS amplify-cli

Compare nodejs-storage vs amplify-cli and see what are their differences.


Node.js client for Google Cloud Storage: unified object storage for developers and enterprises, from live data serving to data analytics/ML to data archiving. (by googleapis)
Our great sponsors
  • Appwrite - The Open Source Firebase alternative introduces iOS support
  • SonarLint - Clean code begins in your IDE with SonarLint
  • - Download’s Tech Salary Report
  • Scout APM - Truly a developer’s best friend
nodejs-storage amplify-cli
5 13
751 2,585
0.9% 1.1%
9.1 9.8
5 days ago 4 days ago
TypeScript TypeScript
Apache License 2.0 Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of nodejs-storage. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-09-11.
  • The Cloud Resume Challenge - GCP :)
    2 projects | | 11 Sep 2022
    The static site (Resume) is supposed to be hosted on Google Cloud Storage and use a cloud load balancer for traffic flow. I used GCP storage bucket to host the site while Cloud Load Balancing via HTTP(S) Load Balancer on GCP.
  • Google Cloud Reference
    24 projects | | 30 Aug 2022
    Cloud Storage: Multi-class multi-region object storage🔗Link 🔗Link
  • System Design: The complete course
    31 projects | | 16 Aug 2022
    We can use object stores like Amazon S3, Azure Blob Storage, or Google Cloud Storage for this use case.


Posts with mentions or reviews of amplify-cli. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-07-09.
  • Amplify UI – Don't just prototype. Connect your UI to the cloud
    2 projects | | 9 Jul 2022
    This disconnection between the initial business cases of DynamoDB and Amplify can even be seen within the AWS teams themselves. [4] We don't believe any of them are to blame. The solo Front End Engineer bootstrapping a quick Amplify app for a PoC feels like a way different use case than a team of highly trained data engineers working on their Single Table Design for their micro-service. Amplify rightfully tries to offer an easy way to deal with storing data. And so it follows a standard SQL design with DynamoDB. This though leads to bad performance (original selling point of DynamoDB) or other limitations hard to anticipate.

    Overall it is pretty clear and fine that Amplify focuses on PoC projects rather than production ones (with features like Geo-tagging [5] but no way to migrate data). However, when starting to get traction, it is a shame we need to completely eject instead of being able to extend because of lack of (boring but necessary) fundamentals.


  • Deploy AWS Amplify GraphQL Transformers with AWS CDK
    5 projects | | 13 Mar 2022
    AWS Amplify code is open-sourced and could be found on GitHub at We could make use of the NPM packages deployed independently to recreate the functionality offered by the AWS Amplify CLI regarding the GraphQL transformers. The entry point for generating the Appsync resolvers could be found here and the class we are interested in is GraphQLTransform which takes as a parameter all the individual transformers and iterates over them to generate the GraphQL resolvers and the associated CloudFormation stacks for deploying those resolvers.
  • MLH, Open Source, Mapillary & Me
    7 projects | | 31 Aug 2021
    AWS Amplify - The AWS Amplify CLI is a toolchain which includes a robust feature set for simplifying mobile and web application development. The CLI uses AWS CloudFormation and nested stacks to allow you to add or modify configurations locally before you push them for execution in your account.
  • Using Free APIs for your own projects.
    2 projects | | 30 Jun 2021
    Just wanted to share my experience as someone who has an app using AppSync and Amplify on the App Store: using the iOS libraries has been painless (though I should note that I'm using the older AppSync SDK), but the Amplify CLI, which I use for the backend, has been a frequent source of frustration. It does a lot of magic which is great when it works, but frustrating when it doesn't. Some of my issues may have been the result of early adoption, but if you are thinking about using it for something with a backend that you are going to continue to maintain and develop, I would suggest considering other AWS options. I'm currently looking into transitioning away from the Amplify CLI to using AWS CDK with the Amplify transformers.
  • Pros and cons of using AWS Amplify
    5 projects | | 28 Dec 2020
    adding environment variables to lambda functions not surprisingly there is a github issue to request this feature. The TLDR is - the Environment variables tab in your Amplify console is used to add build configuration environment variables, not backend function environment variables. So to add lambda environment variables you would have to do that in your AWS Lambda console, for every function individually.
    5 projects | | 28 Dec 2020
    adding permissions to lambda functions to access resources outside the amplify stack in a reliable way. For example you have a lambda function that needs to talk to SES for sending emails, then you would have to grant your lambda permissions for SES actions. However you can't do that using AWS Amplify CLI, and updating the lambdas' permission in the cloudformation template is a no go, because it gets overwritten if you then add permission to the same lambda function using the CLI, which is a very sticky situation, because your only option is to modify the permissions again using the IAM console. More info in the SES permissions issue.
    5 projects | | 28 Dec 2020
    There is no straight forward way to add typescript support for the lambda functions
    5 projects | | 28 Dec 2020
    You could add Aurora serverless datasource to your Graphql API, but no @model support is available. Also the CLI only supports Amazon Aurora MySQL 5.6 dbs running in the us-east-1 region - according to the docs.

What are some alternatives?

When comparing nodejs-storage and amplify-cli you can also consider the following projects:

awesome-readme - A curated list of awesome READMEs

aws-cdk - The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code

antlir - ANother Linux Image buildeR

Terrabuzz - Social media based on connecting users on the basis of interests, integrating a system of news-feed, following/followers, notifications, profile updates, and a basic settings page

howdoi - instant coding answers via the command line

amplify-js - A declarative JavaScript library for application development using cloud services.


aws-lambda-graphql - Use AWS Lambda + AWS API Gateway v2 for GraphQL subscriptions over WebSocket and AWS API Gateway v1 for HTTP

Adequate-Backend - Backend for Adequate, an iOS client for

mapillary-python-sdk - A Python 3 library built on the Mapillary API v4 to facilitate retrieving and working with Mapillary data.

content-analysis-on-aws - This project is a fully automated video search engine which uses AWS AI services for computer vision and speech recognition to catalog video archives.

aws-amplify-cdk - AWS Amplify GraphQL transformers deployed with AWS CDK