Alternatives to Parse-Server logo

Alternatives to Parse-Server

Firebase, Parse, Heroku, MongoDB, and React Native Firebase are the most popular alternatives and competitors to Parse-Server.
176
223
+ 1
31

What is Parse-Server and what are its top alternatives?

A Parse.com API compatible router package for Express. Read the announcement blog post here: http://blog.parse.com/announcements/introducing-parse-server-and-the-database-migration-tool/. Read the migration guide here: https://parse.com/docs/server/guide#migrating
Parse-Server is a tool in the Platform as a Service Tools category of a tech stack.
Parse-Server is an open source tool with GitHub stars and GitHub forks. Here’s a link to Parse-Server's open source repository on GitHub

Top Alternatives to Parse-Server

  • 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. ...

  • Parse
    Parse

    With Parse, you can add a scalable and powerful backend in minutes and launch a full-featured app in record time without ever worrying about server management. We offer push notifications, social integration, data storage, and the ability to add rich custom logic to your app’s backend with Cloud Code. ...

  • Heroku
    Heroku

    Heroku is a cloud application platform – a new way of building and deploying web apps. Heroku lets app developers spend 100% of their time on their application code, not managing servers, deployment, ongoing operations, or scaling. ...

  • MongoDB
    MongoDB

    MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding. ...

  • React Native Firebase
    React Native Firebase

    RNFirebase is a light-weight layer sitting on-top of the native Firebase libraries for both iOS and Android which mirrors the Firebase Web SDK as closely as possible. ...

  • Jungle
    Jungle

    awscli is by far the most comprehensive CLI tool manipulating various AWS services, and I really like its flexible options and up-to-date release cycle. However, day-to-day AWS operations from my terminal don't need that much flexibility and that many services. ...

  • Adept Scale
    Adept Scale

    Adept Scale works by ingesting and processing an application’s syslog drain. With a few parameters found in the settings section, the Adept Scale calculation algorithm will recommend dyno usage and will scale your dynos if necessary. ...

  • HireFire
    HireFire

    is a hosted service for auto-scaling both web- and worker dynos. The service supports practically any worker library across all programming languages through an abstract interface. ...

Parse-Server alternatives & related posts

Firebase logo

Firebase

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

related Firebase posts

Stephen Gheysens
Senior Solutions Engineer at Twilio · | 14 upvotes · 611.5K 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
Tassanai Singprom

This is my stack in Application & Data

JavaScript PHP HTML5 jQuery Redis Amazon EC2 Ubuntu Sass Vue.js Firebase Laravel Lumen Amazon RDS GraphQL MariaDB

My Utilities Tools

Google Analytics Postman Elasticsearch

My Devops Tools

Git GitHub GitLab npm Visual Studio Code Kibana Sentry BrowserStack

My Business Tools

Slack

See more
Parse logo

Parse

423
451
583
The complete mobile app platform
423
451
+ 1
583
PROS OF PARSE
  • 116
    Easy setup
  • 76
    Free hosting
  • 61
    Well-documented
  • 50
    Cheap
  • 46
    Use push notifications in 3 lines of code
  • 40
    Fast
  • 39
    Cloud code
  • 31
    Good for prototypes
  • 30
    Cloud modules
  • 27
    Backed by facebook
  • 7
    Parse Push
  • 7
    Cross Platform
  • 6
    Parse Core
  • 6
    Parse Analytics
  • 5
    Multiplatform
  • 5
    Quick chat and profile capabilities
  • 5
    Free Tier
  • 4
    Cloud Based
  • 3
    Backend as a service
  • 3
    Backbone Models
  • 3
    Nice security concept
  • 3
    Free
  • 3
    Geopoints
  • 2
    Local Datastore
  • 2
    Anonymous Users
  • 2
    Easy to use
  • 1
    About to Die
CONS OF PARSE
    Be the first to leave a con

    related Parse posts

    Heroku logo

    Heroku

    21.8K
    17.2K
    3.2K
    Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience.
    21.8K
    17.2K
    + 1
    3.2K
    PROS OF HEROKU
    • 704
      Easy deployment
    • 459
      Free for side projects
    • 374
      Huge time-saver
    • 348
      Simple scaling
    • 261
      Low devops skills required
    • 190
      Easy setup
    • 174
      Add-ons for almost everything
    • 153
      Beginner friendly
    • 150
      Better for startups
    • 133
      Low learning curve
    • 48
      Postgres hosting
    • 41
      Easy to add collaborators
    • 30
      Faster development
    • 24
      Awesome documentation
    • 19
      Simple rollback
    • 19
      Focus on product, not deployment
    • 15
      Natural companion for rails development
    • 15
      Easy integration
    • 12
      Great customer support
    • 8
      GitHub integration
    • 6
      Painless & well documented
    • 6
      No-ops
    • 4
      I love that they make it free to launch a side project
    • 4
      Free
    • 3
      Great UI
    • 3
      Just works
    • 2
      PostgreSQL forking and following
    • 2
      MySQL extension
    • 1
      Security
    • 1
      Able to host stuff good like Discord Bot
    • 0
      Sec
    CONS OF HEROKU
    • 24
      Super expensive
    • 7
      Not a whole lot of flexibility
    • 5
      No usable MySQL option
    • 5
      Storage
    • 4
      Low performance on free tier
    • 1
      24/7 support is $1,000 per month

    related Heroku posts

    Russel Werner
    Lead Engineer at StackShare · | 31 upvotes · 1.6M views

    StackShare Feed is built entirely with React, Glamorous, and Apollo. One of our objectives with the public launch of the Feed was to enable a Server-side rendered (SSR) experience for our organic search traffic. When you visit the StackShare Feed, and you aren't logged in, you are delivered the Trending feed experience. We use an in-house Node.js rendering microservice to generate this HTML. This microservice needs to run and serve requests independent of our Rails web app. Up until recently, we had a mono-repo with our Rails and React code living happily together and all served from the same web process. In order to deploy our SSR app into a Heroku environment, we needed to split out our front-end application into a separate repo in GitHub. The driving factor in this decision was mostly due to limitations imposed by Heroku specifically with how processes can't communicate with each other. A new SSR app was created in Heroku and linked directly to the frontend repo so it stays in-sync with changes.

    Related to this, we need a way to "deploy" our frontend changes to various server environments without building & releasing the entire Ruby application. We built a hybrid Amazon S3 Amazon CloudFront solution to host our Webpack bundles. A new CircleCI script builds the bundles and uploads them to S3. The final step in our rollout is to update some keys in Redis so our Rails app knows which bundles to serve. The result of these efforts were significant. Our frontend team now moves independently of our backend team, our build & release process takes only a few minutes, we are now using an edge CDN to serve JS assets, and we have pre-rendered React pages!

    #StackDecisionsLaunch #SSR #Microservices #FrontEndRepoSplit

    See more
    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 4.2M views

    Our whole DevOps stack consists of the following tools:

    • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
    • Respectively Git as revision control system
    • SourceTree as Git GUI
    • Visual Studio Code as IDE
    • CircleCI for continuous integration (automatize development process)
    • Prettier / TSLint / ESLint as code linter
    • SonarQube as quality gate
    • Docker as container management (incl. Docker Compose for multi-container application management)
    • VirtualBox for operating system simulation tests
    • Kubernetes as cluster management for docker containers
    • Heroku for deploying in test environments
    • nginx as web server (preferably used as facade server in production environment)
    • SSLMate (using OpenSSL) for certificate management
    • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
    • PostgreSQL as preferred database system
    • Redis as preferred in-memory database/store (great for caching)

    The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

    • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
    • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
    • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
    • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
    • Scalability: All-in-one framework for distributed systems.
    • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
    See more
    MongoDB logo

    MongoDB

    72.2K
    61.1K
    4.1K
    The database for giant ideas
    72.2K
    61.1K
    + 1
    4.1K
    PROS OF MONGODB
    • 828
      Document-oriented storage
    • 593
      No sql
    • 549
      Ease of use
    • 465
      Fast
    • 408
      High performance
    • 256
      Free
    • 215
      Open source
    • 180
      Flexible
    • 143
      Replication & high availability
    • 110
      Easy to maintain
    • 42
      Querying
    • 38
      Easy scalability
    • 37
      Auto-sharding
    • 36
      High availability
    • 31
      Map/reduce
    • 27
      Document database
    • 25
      Full index support
    • 25
      Easy setup
    • 16
      Reliable
    • 15
      Fast in-place updates
    • 14
      Agile programming, flexible, fast
    • 12
      No database migrations
    • 8
      Easy integration with Node.Js
    • 8
      Enterprise
    • 6
      Enterprise Support
    • 5
      Great NoSQL DB
    • 3
      Drivers support is good
    • 3
      Aggregation Framework
    • 3
      Support for many languages through different drivers
    • 2
      Awesome
    • 2
      Schemaless
    • 2
      Managed service
    • 2
      Fast
    • 2
      Easy to Scale
    • 1
      Consistent
    • 1
      Acid Compliant
    CONS OF MONGODB
    • 6
      Very slowly for connected models that require joins
    • 3
      Not acid compliant
    • 1
      Proprietary query language

    related MongoDB posts

    Jeyabalaji Subramanian

    Recently we were looking at a few robust and cost-effective ways of replicating the data that resides in our production MongoDB to a PostgreSQL database for data warehousing and business intelligence.

    We set ourselves the following criteria for the optimal tool that would do this job: - The data replication must be near real-time, yet it should NOT impact the production database - The data replication must be horizontally scalable (based on the load), asynchronous & crash-resilient

    Based on the above criteria, we selected the following tools to perform the end to end data replication:

    We chose MongoDB Stitch for picking up the changes in the source database. It is the serverless platform from MongoDB. One of the services offered by MongoDB Stitch is Stitch Triggers. Using stitch triggers, you can execute a serverless function (in Node.js) in real time in response to changes in the database. When there are a lot of database changes, Stitch automatically "feeds forward" these changes through an asynchronous queue.

    We chose Amazon SQS as the pipe / message backbone for communicating the changes from MongoDB to our own replication service. Interestingly enough, MongoDB stitch offers integration with AWS services.

    In the Node.js function, we wrote minimal functionality to communicate the database changes (insert / update / delete / replace) to Amazon SQS.

    Next we wrote a minimal micro-service in Python to listen to the message events on SQS, pickup the data payload & mirror the DB changes on to the target Data warehouse. We implemented source data to target data translation by modelling target table structures through SQLAlchemy . We deployed this micro-service as AWS Lambda with Zappa. With Zappa, deploying your services as event-driven & horizontally scalable Lambda service is dumb-easy.

    In the end, we got to implement a highly scalable near realtime Change Data Replication service that "works" and deployed to production in a matter of few days!

    See more
    Robert Zuber

    We use MongoDB as our primary #datastore. Mongo's approach to replica sets enables some fantastic patterns for operations like maintenance, backups, and #ETL.

    As we pull #microservices from our #monolith, we are taking the opportunity to build them with their own datastores using PostgreSQL. We also use Redis to cache data we’d never store permanently, and to rate-limit our requests to partners’ APIs (like GitHub).

    When we’re dealing with large blobs of immutable data (logs, artifacts, and test results), we store them in Amazon S3. We handle any side-effects of S3’s eventual consistency model within our own code. This ensures that we deal with user requests correctly while writes are in process.

    See more
    React Native Firebase logo

    React Native Firebase

    88
    113
    4
    A well tested Firebase implementation for React Native, supporting both iOS & Android apps
    88
    113
    + 1
    4
    PROS OF REACT NATIVE FIREBASE
    • 2
      Feature-rich
    • 2
      Well supported
    CONS OF REACT NATIVE FIREBASE
      Be the first to leave a con

      related React Native Firebase posts

      Firebase Cloud Firestore Cloud Functions for Firebase Google App Engine React React Native React Native Firebase NativeBase Twilio Dwolla.js Yarn fastlane Bitbucket Slack LastPass

      See more
      Jungle logo

      Jungle

      32
      38
      0
      Simple CLI for AWS operations
      32
      38
      + 1
      0
      PROS OF JUNGLE
        Be the first to leave a pro
        CONS OF JUNGLE
          Be the first to leave a con

          related Jungle posts

          Adept Scale logo

          Adept Scale

          6
          8
          0
          Automated Scaling of Heroku Dynos
          6
          8
          + 1
          0
          PROS OF ADEPT SCALE
            Be the first to leave a pro
            CONS OF ADEPT SCALE
              Be the first to leave a con

              related Adept Scale posts

              HireFire logo

              HireFire

              4
              3
              0
              Autoscaling for your Heroku dynos
              4
              3
              + 1
              0
              PROS OF HIREFIRE
                Be the first to leave a pro
                CONS OF HIREFIRE
                  Be the first to leave a con

                  related HireFire posts