Alternatives to GitHub Pages logo

Alternatives to GitHub Pages

Netlify, GitLab Pages, Amazon S3, Medium, and WordPress are the most popular alternatives and competitors to GitHub Pages.
17.5K
12.7K
+ 1
1.1K

What is GitHub Pages and what are its top alternatives?

Public webpages hosted directly from your GitHub repository. Just edit, push, and your changes are live.
GitHub Pages is a tool in the Static Web Hosting category of a tech stack.

Top Alternatives to GitHub Pages

  • Netlify
    Netlify

    Netlify is smart enough to process your site and make sure all assets gets optimized and served with perfect caching-headers from a cookie-less domain. We make sure your HTML is served straight from our CDN edge nodes without any round-trip to our backend servers and are the only ones to give you instant cache invalidation when you push a new deploy. Netlify is also the only static hosting service with integrated continuous deployment. ...

  • GitLab Pages
    GitLab Pages

    Host your static websites on GitLab.com for free, or on your own GitLab Enterprise Edition instance. Use any static website generator: Jekyll, Middleman, Hexo, Hugo, Pelican, and more ...

  • Amazon S3
    Amazon S3

    Amazon Simple Storage Service provides a fully redundant data storage infrastructure for storing and retrieving any amount of data, at any time, from anywhere on the web ...

  • Medium
    Medium

    Medium is a different kind of place on the internet. A place where the measure of success isn’t views, but viewpoints. Where the quality of the idea matters, not the author’s qualifications. A place where conversation pushes ideas forward. ...

  • WordPress
    WordPress

    The core software is built by hundreds of community volunteers, and when you’re ready for more there are thousands of plugins and themes available to transform your site into almost anything you can imagine. Over 60 million people have chosen WordPress to power the place on the web they call “home” — we’d love you to join the family. ...

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

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

  • Firebase Hosting
    Firebase Hosting

    It is production-grade web content hosting for developers. With a single command, you can quickly deploy web apps and serve both static and dynamic content to a global CDN (content delivery network). You can also pair it with Cloud Functions or Cloud Run to build and host microservices. ...

GitHub Pages alternatives & related posts

Netlify logo

Netlify

3.4K
2K
206
Build, deploy and host your static site or app with a drag and drop interface and automatic delpoys...
3.4K
2K
+ 1
206
PROS OF NETLIFY
  • 46
    Easy deploy
  • 43
    Fastest static hosting and continuous deployments
  • 22
    Free SSL support
  • 22
    Super simple deploys
  • 15
    Easy Setup and Continous deployments
  • 10
    Faster than any other option in the market
  • 10
    Free plan for personal websites
  • 8
    Deploy previews
  • 6
    Free Open Source (Pro) plan
  • 4
    Easy to use and great support
  • 4
    Analytics
  • 4
    Great loop-in material on a blog
  • 3
    Custom domains support
  • 3
    Fastest static hosting and continuous deployments
  • 3
    Great drag and drop functionality
  • 1
    Canary Releases (Split Tests)
  • 1
    Supports static site generators
  • 1
    Tech oriented support
  • 0
    Django
CONS OF NETLIFY
  • 7
    It's expensive
  • 1
    Bandwidth limitation

related Netlify posts

Johnny Bell

I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

See more
Jeyabalaji Subramanian

At FundsCorner, we are on a mission to enable fast accessible credit to India’s Kirana Stores. We are an early stage startup with an ultra small Engineering team. All the tech decisions we have made until now are based on our core philosophy: "Build usable products fast".

Based on the above fundamentals, we chose Python as our base language for all our APIs and micro-services. It is ultra easy to start with, yet provides great libraries even for the most complex of use cases. Our entire backend stack runs on Python and we cannot be more happy with it! If you are looking to deploy your API as server-less, Python provides one of the least cold start times.

We build our APIs with Flask. For backend database, our natural choice was MongoDB. It frees up our time from complex database specifications - we instead use our time in doing sensible data modelling & once we finalize the data model, we integrate it into Flask using Swagger UI. Mongo supports complex queries to cull out difficult data through aggregation framework & we have even built an internal framework called "Poetry", for aggregation queries.

Our web apps are built on Vue.js , Vuetify and vuex. Initially we debated a lot around choosing Vue.js or React , but finally settled with Vue.js, mainly because of the ease of use, fast development cycles & awesome set of libraries and utilities backing Vue.

You simply cannot go wrong with Vue.js . Great documentation, the library is ultra compact & is blazing fast. Choosing Vue.js was one of the critical decisions made, which enabled us to launch our web app in under a month (which otherwise would have taken 3 months easily). For those folks who are looking for big names, Adobe, and Alibaba and Gitlab are using Vue.

By choosing Vuetify, we saved thousands of person hours in designing the CSS files. Vuetify contains all key material components for designing a smooth User experience & it just works! It's an awesome framework. All of us at FundsCorner are now lifelong fanboys of Vue.js and Vuetify.

On the infrastructure side, all our API services and backend services are deployed as server less micro-services through Zappa. Zappa makes your life super easy by packaging everything that is required to deploy your code as AWS Lambda. We are now addicted to the single - click deploys / updates through Zappa. Try it out & you will convert!

Also, if you are using Zappa, you can greatly simplify your CI / CD pipelines. Do try it! It's just awesome! and... you will be astonished by the savings you have made on AWS bills at end of the month.

Our CI / CD pipelines are built using GitLab CI. The documentation is very good & it enables you to go from from concept to production in minimal time frame.

We use Sentry for all crash reporting and resolution. Pro tip, they do have handlers for AWS Lambda , which made our integration super easy.

All our micro-services including APIs are event-driven. Our background micro-services are message oriented & we use Amazon SQS as our message pipe. We have our own in-house workflow manager to orchestrate across micro - services.

We host our static websites on Netlify. One of the cool things about Netlify is the automated CI / CD on git push. You just do a git push to deploy! Again, it is super simple to use and it just works. We were dogmatic about going server less even on static web sites & you can go server less on Netlify in a few minutes. It's just a few clicks away.

We use Google Compute Engine, especially Google Vision for our AI experiments.

For Ops automation, we use Slack. Slack provides a super-rich API (through Slack App) through which you can weave magical automation on boring ops tasks.

See more
GitLab Pages logo

GitLab Pages

249
296
11
Create websites for your GitLab projects, groups, or user account
249
296
+ 1
11
PROS OF GITLAB PAGES
  • 5
    Free
  • 4
    Integrated build and release pipeline
  • 2
    Allows any custom build scripts and plugins
CONS OF GITLAB PAGES
  • 1
    Require Jekyll approach
  • 0
    Slow builds

related GitLab Pages posts

Joshua Dean Küpper
CEO at Scrayos UG (haftungsbeschränkt) · | 20 upvotes · 703.6K views

We use GitLab CI because of the great native integration as a part of the GitLab framework and the linting-capabilities it offers. The visualization of complex pipelines and the embedding within the project overview made Gitlab CI even more convenient. We use it for all projects, all deployments and as a part of GitLab Pages.

While we initially used the Shell-executor, we quickly switched to the Docker-executor and use it exclusively now.

We formerly used Jenkins but preferred to handle everything within GitLab . Aside from the unification of our infrastructure another motivation was the "configuration-in-file"-approach, that Gitlab CI offered, while Jenkins support of this concept was very limited and users had to resort to using the webinterface. Since the file is included within the repository, it is also version controlled, which was a huge plus for us.

See more
Michael Kelly
Senior Software Engineer at StackShare · | 14 upvotes · 950.5K views

I use GitLab when building side-projects and MVPs. The interface and interactions are close enough to those of GitHub to prevent cognitive switching costs between professional and personal projects hosted on different services.

GitLab also provides a suite of tools including issue/project management, CI/CD with GitLab CI, and validation/landing pages with GitLab Pages. With everything in one place, on an #OpenSourceCloud GitLab makes it easy for me to manage much larger projects on my own, than would be possible with other solutions or tools.

It's petty I know, but I can also read the GitLab code diffs far more easily than diffs on GitHub or Bitbucket...they just look better in my opinion.

See more
Amazon S3 logo

Amazon S3

52.8K
39.5K
2K
Store and retrieve any amount of data, at any time, from anywhere on the web
52.8K
39.5K
+ 1
2K
PROS OF AMAZON S3
  • 590
    Reliable
  • 492
    Scalable
  • 456
    Cheap
  • 329
    Simple & easy
  • 83
    Many sdks
  • 30
    Logical
  • 13
    Easy Setup
  • 11
    REST API
  • 11
    1000+ POPs
  • 6
    Secure
  • 4
    Plug and play
  • 4
    Easy
  • 3
    Web UI for uploading files
  • 2
    Faster on response
  • 2
    Flexible
  • 2
    GDPR ready
  • 1
    Easy to use
  • 1
    Plug-gable
  • 1
    Easy integration with CloudFront
CONS OF AMAZON S3
  • 7
    Permissions take some time to get right
  • 6
    Requires a credit card
  • 6
    Takes time/work to organize buckets & folders properly
  • 3
    Complex to set up

related Amazon S3 posts

Ashish Singh
Tech Lead, Big Data Platform at Pinterest · | 38 upvotes · 3M views

To provide employees with the critical need of interactive querying, we’ve worked with Presto, an open-source distributed SQL query engine, over the years. Operating Presto at Pinterest’s scale has involved resolving quite a few challenges like, supporting deeply nested and huge thrift schemas, slow/ bad worker detection and remediation, auto-scaling cluster, graceful cluster shutdown and impersonation support for ldap authenticator.

Our infrastructure is built on top of Amazon EC2 and we leverage Amazon S3 for storing our data. This separates compute and storage layers, and allows multiple compute clusters to share the S3 data.

We have hundreds of petabytes of data and tens of thousands of Apache Hive tables. Our Presto clusters are comprised of a fleet of 450 r4.8xl EC2 instances. Presto clusters together have over 100 TBs of memory and 14K vcpu cores. Within Pinterest, we have close to more than 1,000 monthly active users (out of total 1,600+ Pinterest employees) using Presto, who run about 400K queries on these clusters per month.

Each query submitted to Presto cluster is logged to a Kafka topic via Singer. Singer is a logging agent built at Pinterest and we talked about it in a previous post. Each query is logged when it is submitted and when it finishes. When a Presto cluster crashes, we will have query submitted events without corresponding query finished events. These events enable us to capture the effect of cluster crashes over time.

Each Presto cluster at Pinterest has workers on a mix of dedicated AWS EC2 instances and Kubernetes pods. Kubernetes platform provides us with the capability to add and remove workers from a Presto cluster very quickly. The best-case latency on bringing up a new worker on Kubernetes is less than a minute. However, when the Kubernetes cluster itself is out of resources and needs to scale up, it can take up to ten minutes. Some other advantages of deploying on Kubernetes platform is that our Presto deployment becomes agnostic of cloud vendor, instance types, OS, etc.

#BigData #AWS #DataScience #DataEngineering

See more
Russel Werner
Lead Engineer at StackShare · | 32 upvotes · 2.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
Medium logo

Medium

767
689
190
The perfect place to read and write.
767
689
+ 1
190
PROS OF MEDIUM
  • 61
    Beautiful UI
  • 34
    Typography
  • 15
    Network effect
  • 12
    Embedding videos, tweets, vines
  • 12
    Great mobile app
  • 11
    Simple, yet elegant and appealing UX
  • 10
    Notes
  • 9
    Word counter
  • 7
    Easy to gain traction
  • 4
    Idealized media consumption
  • 3
    Inline Comments & Discussions
  • 3
    Beautiful design. great content, excellent experience
  • 2
    Version history
  • 2
    Nice UI and UX
  • 2
    Embed medium
  • 2
    Recommendations
  • 1
    Daily Digest
CONS OF MEDIUM
    Be the first to leave a con

    related Medium posts

    WordPress logo

    WordPress

    96.5K
    39K
    2.1K
    A semantic personal publishing platform with a focus on aesthetics, web standards, and usability.
    96.5K
    39K
    + 1
    2.1K
    PROS OF WORDPRESS
    • 415
      Customizable
    • 366
      Easy to manage
    • 354
      Plugins & themes
    • 258
      Non-tech colleagues can update website content
    • 247
      Really powerful
    • 145
      Rapid website development
    • 78
      Best documentation
    • 51
      Codex
    • 44
      Product feature set
    • 35
      Custom/internal social network
    • 18
      Open source
    • 8
      Great for all types of websites
    • 7
      Huge install and user base
    • 5
      Perfect example of user collaboration
    • 5
      Open Source Community
    • 5
      Most websites make use of it
    • 5
      It's simple and easy to use by any novice
    • 5
      Best
    • 5
      I like it like I like a kick in the groin
    • 4
      Community
    • 4
      API-based CMS
    • 3
      Easy To use
    • 2
      <a href="https://secure.wphackedhel">Easy Beginner</a>
    CONS OF WORDPRESS
    • 13
      Hard to keep up-to-date if you customize things
    • 13
      Plugins are of mixed quality
    • 10
      Not best backend UI
    • 2
      Complex Organization
    • 1
      Do not cover all the basics in the core
    • 1
      Great Security

    related WordPress posts

    Dale Ross
    Independent Contractor at Self Employed · | 22 upvotes · 1.6M views

    I've heard that I have the ability to write well, at times. When it flows, it flows. I decided to start blogging in 2013 on Blogger. I started a company and joined BizPark with the Microsoft Azure allotment. I created a WordPress blog and did a migration at some point. A lot happened in the time after that migration but I stopped coding and changed cities during tumultuous times that taught me many lessons concerning mental health and productivity. I eventually graduated from BizSpark and outgrew the credit allotment. That killed the WordPress blog.

    I blogged about writing again on the existing Blogger blog but it didn't feel right. I looked at a few options where I wouldn't have to worry about hosting cost indefinitely and Jekyll stood out with GitHub Pages. The Importer was fairly straightforward for the existing blog posts.

    Todo * Set up redirects for all posts on blogger. The URI format is different so a complete redirect wouldn't work. Although, there may be something in Jekyll that could manage the redirects. I did notice the old URLs were stored in the front matter. I'm working on a command-line Ruby gem for the current plan. * I did find some of the lost WordPress posts on archive.org that I downloaded with the waybackmachinedownloader. I think I might write an importer for that. * I still have a few Disqus comment threads to map

    See more
    A White
    Front End Web Dev at Burnt Design · | 21 upvotes · 80.1K views

    Below is my own professional history to give some context to my current skill set. I have been a front-end dev for 18 years. My tools of choice are:

    • HTML5
    • CSS 3
    • JavaScript
    • WordPress
    • PHP (but not my strongest skill as I don't write it too often)

    I first of all would like to become a better and more 'full stack' developer, and I have a business idea that will hopefully allow me to move in this direction. The queries I have will result in which approach I take here. One of the most important aspects to me is the system being 'future proof'. If successful I know I will eventually bring additional developers on board, and they will likely be better developers than me! I want to avoid them having to rebuild the system and would like it to be something that they can just expand and improve on.

    The business which I'd like to create is the following (in a nutshell), I have ideas for many more features, but this is how I'd like to begin:

    Web-based system for gym management & marketing. Specifically a class-based gym

    1. One-stop shop for a class-based gym owner
    2. Sell memberships
    3. Manage class bookings
    4. Reporting
    5. Automatically generated website
    6. Choose a pre-designed template and amend the content through their dashboard
    7. Marketing
    8. Easily send a newsletter to members
    9. Book a free trial form on the website linked directly to the booking system

    Important requirements

    1. One system, one dashboard. I would like the gym owner to have one place to control everything. Members, marketing, and website amendments.
    2. Future proof. These features are the bare minimum and I'd like to keep expanding on the features as time goes on. Things like uploading programming for members, messaging between members and admin, and selling merchandise via the website.
    3. Fast to load & secure. I live in the WordPress world right now, which isn't the fastest or most secure environment. I appreciate there are better ways to develop a system like this, but I'm a little clueless about where to start.
    4. Mobile. The data created should easily communicate with a mobile app that customers will download to manage their memberships and class bookings.

    TIA to anybody that can provide some guidance on where to start here.

    See more
    Heroku logo

    Heroku

    25.4K
    20.2K
    3.2K
    Build, deliver, monitor and scale web apps and APIs with a trail blazing developer experience.
    25.4K
    20.2K
    + 1
    3.2K
    PROS OF HEROKU
    • 703
      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
    • 27
      Super expensive
    • 9
      Not a whole lot of flexibility
    • 7
      No usable MySQL option
    • 7
      Storage
    • 5
      Low performance on free tier
    • 2
      24/7 support is $1,000 per month

    related Heroku posts

    Russel Werner
    Lead Engineer at StackShare · | 32 upvotes · 2.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 · | 30 upvotes · 10M 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
    Firebase logo

    Firebase

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

    related Firebase posts

    Johnny Bell

    I was building a personal project that I needed to store items in a real time database. I am more comfortable with my Frontend skills than my backend so I didn't want to spend time building out anything in Ruby or Go.

    I stumbled on Firebase by #Google, and it was really all I needed. It had realtime data, an area for storing file uploads and best of all for the amount of data I needed it was free!

    I built out my application using tools I was familiar with, React for the framework, Redux.js to manage my state across components, and styled-components for the styling.

    Now as this was a project I was just working on in my free time for fun I didn't really want to pay for hosting. I did some research and I found Netlify. I had actually seen them at #ReactRally the year before and deployed a Gatsby site to Netlify already.

    Netlify was very easy to setup and link to my GitHub account you select a repo and pretty much with very little configuration you have a live site that will deploy every time you push to master.

    With the selection of these tools I was able to build out my application, connect it to a realtime database, and deploy to a live environment all with $0 spent.

    If you're looking to build out a small app I suggest giving these tools a go as you can get your idea out into the real world for absolutely no cost.

    See more
    Collins Ogbuzuru
    Front-end dev at Evolve credit · | 20 upvotes · 27.3K views

    Your tech stack is solid for building a real-time messaging project.

    React and React Native are excellent choices for the frontend, especially if you want to have both web and mobile versions of your application share code.

    ExpressJS is an unopinionated framework that affords you the flexibility to use it's features at your term, which is a good start. However, I would recommend you explore Sails.js as well. Sails.js is built on top of Express.js and it provides additional features out of the box, especially the Websocket integration that your project requires.

    Don't forget to set up Graphql codegen, this would improve your dev experience (Add Typescript, if you can too).

    I don't know much about databases but you might want to consider using NO-SQL. I used Firebase real-time db and aws dynamo db on a few of my personal projects and I love they're easy to work with and offer more flexibility for a chat application.

    See more
    Firebase Hosting logo

    Firebase Hosting

    178
    176
    10
    Production-grade web content hosting
    178
    176
    + 1
    10
    PROS OF FIREBASE HOSTING
    • 4
      Integration with firebase
    • 1
      Custom domain setup
    • 1
      Free SSL Support
    • 1
      Multi-site hosting support
    • 1
      Analytics
    • 1
      Super simple deploys
    • 1
      Easy deployment
    CONS OF FIREBASE HOSTING
      Be the first to leave a con

      related Firebase Hosting posts