Alternatives to Parse logo

Alternatives to Parse

Firebase, Heroku, DreamFactory, Parse-Server, and Realm are the most popular alternatives and competitors to Parse.
356
303
+ 1
545

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鈥檚 backend with Cloud Code.
Parse is a tool in the Mobile Backend category of a tech stack.

Parse alternatives & related posts

related Firebase posts

fontumi
fontumi
Firebase
Firebase
Node.js
Node.js
FeathersJS
FeathersJS
Vue.js
Vue.js
Google Compute Engine
Google Compute Engine
Dialogflow
Dialogflow
Cloud Firestore
Cloud Firestore
Git
Git
GitHub
GitHub
Visual Studio Code
Visual Studio Code

Fontumi focuses on the development of telecommunications solutions. We have opted for technologies that allow agile development and great scalability.

Firebase and Node.js + FeathersJS are technologies that we have used on the server side. Vue.js is our main framework for clients.

Our latest products launched have been focused on the integration of AI systems for enriched conversations. Google Compute Engine , along with Dialogflow and Cloud Firestore have been important tools for this work.

Git + GitHub + Visual Studio Code is a killer stack.

See more
Aliadoc Team
Aliadoc Team
at aliadoc.com | 5 upvotes 122.4K views
atAliadocAliadoc
React
React
Create React App
Create React App
CloudFlare
CloudFlare
Firebase
Firebase
Cloud Functions for Firebase
Cloud Functions for Firebase
Google App Engine
Google App Engine
Google Cloud Storage
Google Cloud Storage
Serverless
Serverless
Visual Studio Code
Visual Studio Code
Bitbucket
Bitbucket
#Aliadoc

In #Aliadoc, we're exploring the crowdfunding option to get traction before launch. We are building a SaaS platform for website design customization.

For the Admin UI and website editor we use React and we're currently transitioning from a Create React App setup to a custom one because our needs have become more specific. We use CloudFlare as much as possible, it's a great service.

For routing dynamic resources and proxy tasks to feed websites to the editor we leverage CloudFlare Workers for improved responsiveness. We use Firebase for our hosting needs and user authentication while also using several Cloud Functions for Firebase to interact with other services along with Google App Engine and Google Cloud Storage, but also the Real Time Database is on the radar for collaborative website editing.

We generally hate configuration but honestly because of the stage of our project we lack resources for doing heavy sysops work. So we are basically just relying on Serverless technologies as much as we can to do all server side processing.

Visual Studio Code definitively makes programming a much easier and enjoyable task, we just love it. We combine it with Bitbucket for our source code control needs.

See more
Heroku logo

Heroku

8.1K
5.7K
3.1K
8.1K
5.7K
+ 1
3.1K
Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience.
Heroku logo
Heroku
VS
Parse logo
Parse

related Heroku posts

Tim Nolet
Tim Nolet
Founder, Engineer & Dishwasher at Checkly | 19 upvotes 275.7K views
atChecklyHQChecklyHQ
Heroku
Heroku
Docker
Docker
GitHub
GitHub
Node.js
Node.js
hapi
hapi
Vue.js
Vue.js
AWS Lambda
AWS Lambda
Amazon S3
Amazon S3
PostgreSQL
PostgreSQL
Knex.js
Knex.js
vuex
vuex

Heroku Docker GitHub Node.js hapi Vue.js AWS Lambda Amazon S3 PostgreSQL Knex.js Checkly is a fairly young company and we're still working hard to find the correct mix of product features, price and audience.

We are focussed on tech B2B, but I always wanted to serve solo developers too. So I decided to make a $7 plan.

Why $7? Simply put, it seems to be a sweet spot for tech companies: Heroku, Docker, Github, Appoptics (Librato) all offer $7 plans. They must have done a ton of research into this, so why not piggy back that and try it out.

Enough biz talk, onto tech. The challenges were:

  • Slice of a portion of the functionality so a $7 plan is still profitable. We call this the "plan limits"
  • Update API and back end services to handle and enforce plan limits.
  • Update the UI to kindly state plan limits are in effect on some part of the UI.
  • Update the pricing page to reflect all changes.
  • Keep the actual processing backend, storage and API's as untouched as possible.

In essence, we went from strictly volume based pricing to value based pricing. Here come the technical steps & decisions we made to get there.

  1. We updated our PostgreSQL schema so plans now have an array of "features". These are string constants that represent feature toggles.
  2. The Vue.js frontend reads these from the vuex store on login.
  3. Based on these values, the UI has simple v-if statements to either just show the feature or show a friendly "please upgrade" button.
  4. The hapi API has a hook on each relevant API endpoint that checks whether a user's plan has the feature enabled, or not.

Side note: We offer 10 SMS messages per month on the developer plan. However, we were not actually counting how many people were sending. We had to update our alerting daemon (that runs on Heroku and triggers SMS messages via AWS SNS) to actually bump a counter.

What we build is basically feature-toggling based on plan features. It is very extensible for future additions. Our scheduling and storage backend that actually runs users' monitoring requests (AWS Lambda) and stores the results (S3 and Postgres) has no knowledge of all of this and remained unchanged.

Hope this helps anyone building out their SaaS and is in a similar situation.

See more
Russel Werner
Russel Werner
Lead Engineer at StackShare | 19 upvotes 243.1K views
atStackShareStackShare
React
React
Glamorous
Glamorous
Apollo
Apollo
Node.js
Node.js
Rails
Rails
Heroku
Heroku
GitHub
GitHub
Amazon S3
Amazon S3
Amazon CloudFront
Amazon CloudFront
Webpack
Webpack
CircleCI
CircleCI
Redis
Redis
#StackDecisionsLaunch
#SSR
#Microservices
#FrontEndRepoSplit

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
DreamFactory logo

DreamFactory

30
40
18
30
40
+ 1
18
Open source REST API backend for mobile, web, and IoT applications.
DreamFactory logo
DreamFactory
VS
Parse logo
Parse

related Parse-Server posts

Parse-Server
Parse-Server

easy programming model Parse-Server

See more
Realm logo

Realm

121
73
9
121
73
+ 1
9
Realm makes it easy to build reactive apps, realtime collaborative features, and offline-first experiences.
Realm logo
Realm
VS
Parse logo
Parse
Appcelerator logo

Appcelerator

38
28
18
38
28
+ 1
18
Build network-connected mobile applications across native platforms and the web
Appcelerator logo
Appcelerator
VS
Parse logo
Parse
OutSystems logo

OutSystems

16
14
0
16
14
+ 1
0
A low-code platform that lets you visually develop your entire application,
    Be the first to leave a pro
    OutSystems logo
    OutSystems
    VS
    Parse logo
    Parse
    AWS Mobile Hub logo

    AWS Mobile Hub

    12
    22
    0
    12
    22
    + 1
    0
    Build, test, and monitor usage of your mobile apps
      Be the first to leave a pro
      AWS Mobile Hub logo
      AWS Mobile Hub
      VS
      Parse logo
      Parse
      Kinvey logo

      Kinvey

      9
      16
      6
      9
      16
      + 1
      6
      Cloud Backend as a Service for any app.
      Kinvey logo
      Kinvey
      VS
      Parse logo
      Parse
      Mendix logo

      Mendix

      5
      0
      0
      5
      0
      + 1
      0
      Low-code platform used by businesses to develop mobile & web apps
        Be the first to leave a pro
        Mendix logo
        Mendix
        VS
        Parse logo
        Parse
        StackMob logo

        StackMob

        2
        6
        0
        2
        6
        + 1
        0
        Build, Deploy and Grow your mobile applications.
          Be the first to leave a pro
          StackMob logo
          StackMob
          VS
          Parse logo
          Parse
          Cloudmine logo

          Cloudmine

          2
          3
          0
          2
          3
          + 1
          0
          Build & Scale Your Apps In Less Time
            Be the first to leave a pro
            Cloudmine logo
            Cloudmine
            VS
            Parse logo
            Parse