Alternatives to Back4App logo

Alternatives to Back4App

Heroku, Firebase, Parse, Backendless, and Kinvey are the most popular alternatives and competitors to Back4App.
8
24
+ 1
13

What is Back4App and what are its top alternatives?

It allows developers to create apps faster building the backend with no code, host with no infrastructure hassles and scale with no technical locks.
Back4App is a tool in the Realtime Backend / API category of a tech stack.
Back4App is an open source tool with GitHub stars and GitHub forks. Here’s a link to Back4App's open source repository on GitHub

Top Alternatives to Back4App

Back4App alternatives & related posts

related Heroku posts

Russel Werner
Russel Werner
Lead Engineer at StackShare · | 28 upvotes · 1.1M 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
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 24 upvotes · 612.8K 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

related Firebase posts

Tassanai Singprom
Tassanai Singprom
Web Developer · | 10 upvotes · 1.3M views

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

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

Backendless

2
15
0
A mobile Backend as a Service (mBaaS) platform
2
15
+ 1
0
PROS OF BACKENDLESS
    Be the first to leave a pro
    CONS OF BACKENDLESS
      Be the first to leave a con
      Kinvey logo

      Kinvey

      14
      29
      8
      Cloud Backend as a Service for any app.
      14
      29
      + 1
      8
      Parse-Server logo

      Parse-Server

      141
      156
      23
      Parse-compatible API server module for Node/Express
      141
      156
      + 1
      23

      related Parse-Server posts

      Shared insights
      on
      Parse-ServerParse-Server

      easy programming model Parse-Server

      See more

      related Socket.IO posts

      across_the_grid
      across_the_grid
      Full-stack web developer at Capmo GmbH · | 10 upvotes · 219.6K views
      Shared insights
      on
      Socket.IOSocket.IONode.jsNode.jsExpressJSExpressJS

      I use Socket.IO because the application has 2 frontend clients, which need to communicate in real-time. The backend-server handles the communication between these two clients via websockets. Socket.io is very easy to set up in Node.js and ExpressJS.

      In the research project, the 1st client shows panoramic videos in a so called cave system (it is the VR setup of our research lab, which consists of three big screens, which are specially arranged, so the user experience the videos more immersive), the 2nd client controls the videos/locations of the 1st client.

      See more

      I have always been interested in building a real-time multiplayer game engine that could be massively scalable, and recently I decided to start working on a MMO version of the classic "snake" game. I wanted the entire #Stack to be based on ES6 JavaScript so for the #Backend I chose to use FeathersJS with MongoDB for game/user data storage, Redis for distributed mutex and pub/sub, and Socket.IO for real-time communication. For the #Frontend I used React with Redux.js, the FeathersJS client as well as HTML5 canvas to render the view.

      See more
      Pusher logo

      Pusher

      439
      704
      223
      Hosted APIs to build realtime apps with less code
      439
      704
      + 1
      223

      related Pusher posts

      Which messaging service (Pusher vs. PubNub vs. Google Cloud Pub/Sub) to use for IoT?

      See more
      Kirill Shirinkin
      Kirill Shirinkin
      Cloud and DevOps Consultant at mkdev · | 3 upvotes · 81K views
      Shared insights
      on
      MattermostMattermostPusherPusherTwilioTwilio
      at

      Recently we finished long research on chat tool for our students and mentors. In the end we picked Mattermost Team Edition as the cheapest and most feature complete option. We did consider building everything from scratch and use something like Pusher or Twilio on a backend, but then we would have to implement all the desktop and mobile clients and all the features oursevles. Mattermost gave us flexible API, lots of built in or easy to install integrations and future-proof feature set. We are still integrating it with our main platform but so far the team, existing mentors and students are very happy.

      See more