Alternatives to Parse logo

Alternatives to Parse

Firebase, Heroku, DreamFactory, Parse-Server, and Realm are the most popular alternatives and competitors to Parse.
426
455
+ 1
597

What is Parse and what are its top alternatives?

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.
Parse is a tool in the Mobile Backend category of a tech stack.

Top Alternatives to Parse

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

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

  • DreamFactory
    DreamFactory

    DreamFactory is an open source REST API backend for mobile, web, and IoT applications. It provides RESTful web services with pre-built connectors to SQL, NoSQL, file storage systems, and web services. It's secure, reusable, and offers live API documentation. ...

  • Parse-Server
    Parse-Server

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

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

  • OutSystems
    OutSystems

    OutSystems is a low-code platform to visually develop your application, integrate with existing systems and add your own code when needed. ...

  • Appcelerator
    Appcelerator

    Appcelerator is the first mobile platform to combine the flexibility of open source development technologies with the power of cloud services. ...

  • Mendix
    Mendix

    It is a low-code software platform. It provides tools to build, test, deploy and iterate applications. ...

Parse alternatives & related posts

Firebase logo

Firebase

32.7K
28K
1.9K
The Realtime App Platform
32.7K
28K
+ 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
    Super fast development
  • 8
    Angularfire is an amazing addition!
  • 8
    Chat
  • 6
    Built in user auth/oauth
  • 6
    Firebase hosting
  • 6
    Ios adaptor
  • 6
    Awesome next-gen backend
  • 4
    Speed of light
  • 4
    Very easy to use
  • 3
    It's made development super fast
  • 3
    Great
  • 3
    Brilliant for startups
  • 2
    The concurrent updates create a great experience
  • 2
    Cloud functions
  • 2
    Free hosting
  • 2
    Push notification
  • 2
    Free authentication solution
  • 2
    JS Offline and Sync suport
  • 2
    Low battery consumption
  • 2
    I can quickly create static web apps with no backend
  • 2
    Great all-round functionality
  • 1
    Large
  • 1
    Easy to use
  • 1
    Free SSL
  • 1
    CDN & cache out of the box
  • 1
    Faster workflow
  • 1
    .net
  • 1
    Easy Reactjs integration
  • 1
    Google's support
  • 1
    Good Free Limits
  • 1
    Serverless
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
    Very unstable server
  • 3
    No Relational Data
  • 2
    No offline sync
  • 2
    Too many errors

related Firebase posts

Stephen Gheysens
Senior Solutions Engineer at Twilio · | 14 upvotes · 690.7K 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
Heroku logo

Heroku

22.2K
17.7K
3.2K
Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience.
22.2K
17.7K
+ 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 · | 32 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.4M 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
DreamFactory logo

DreamFactory

37
76
20
Open source REST API backend for mobile, web, and IoT applications.
37
76
+ 1
20
PROS OF DREAMFACTORY
  • 6
    Restful
  • 6
    Easy setup
  • 4
    SQL Rest APIS
  • 2
    Love this to easily build API's
  • 1
    Great customer support
  • 1
    Multi Platform
CONS OF DREAMFACTORY
    Be the first to leave a con

    related DreamFactory posts

    Parse-Server logo

    Parse-Server

    178
    227
    31
    Parse-compatible API server module for Node/Express
    178
    227
    + 1
    31
    PROS OF PARSE-SERVER
    • 13
      Open Source
    • 6
      Well documented
    • 4
      Easy setup, easy api, Fast,more platforms,realtime
    • 3
      No vendor lock-in
    • 2
      JSON
    • 2
      Backed by People
    • 1
      Friendly contributor community
    CONS OF PARSE-SERVER
    • 1
      No guarantee (comes as is)

    related Parse-Server posts

    Realm logo

    Realm

    225
    384
    16
    Realm makes it easy to build reactive apps, realtime collaborative features, and offline-first experiences.
    225
    384
    + 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

    OutSystems logo

    OutSystems

    62
    83
    0
    A low-code platform that lets you visually develop your entire application,
    62
    83
    + 1
    0
    PROS OF OUTSYSTEMS
      Be the first to leave a pro
      CONS OF OUTSYSTEMS
      • 0
        Maturidade
      • 0
        Perfomamnce

      related OutSystems posts

      Appcelerator logo

      Appcelerator

      49
      64
      27
      Build network-connected mobile applications across native platforms and the web
      49
      64
      + 1
      27
      PROS OF APPCELERATOR
      • 5
        Android
      • 4
        Open Source
      • 4
        Easy to learn
      • 2
        Great community
      • 2
        Javascript
      • 2
        IOS
      • 1
        Angular.js beta
      • 1
        Vue.js beta
      • 1
        Native UI
      • 1
        Lots of native modules, components, libraries
      • 1
        MVC-based
      • 1
        Paid plans available
      • 1
        Free
      • 1
        Write directly to iOS and Android SDK with JavaScript
      CONS OF APPCELERATOR
      • 1
        No online IDE

      related Appcelerator posts

      Mendix logo

      Mendix

      29
      40
      0
      Low-code platform used by businesses to develop mobile & web apps
      29
      40
      + 1
      0
      PROS OF MENDIX
        Be the first to leave a pro
        CONS OF MENDIX
          Be the first to leave a con

          related Mendix posts