Alternatives to Django REST framework logo

Alternatives to Django REST framework

Django, Flask, Tastypie, Swagger UI, and Graphene are the most popular alternatives and competitors to Django REST framework.
1.8K
1.9K
+ 1
304

What is Django REST framework and what are its top alternatives?

It is a powerful and flexible toolkit that makes it easy to build Web APIs.
Django REST framework is a tool in the Microframeworks (Backend) category of a tech stack.
Django REST framework is an open source tool with GitHub stars and GitHub forks. Here’s a link to Django REST framework's open source repository on GitHub

Top Alternatives to Django REST framework

  • Django
    Django

    Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design. ...

  • Flask
    Flask

    Flask is intended for getting started very quickly and was developed with best intentions in mind. ...

  • Tastypie
    Tastypie

    Tastypie is a webservice API framework for Django. It provides a convenient, yet powerful and highly customizable abstraction for creating REST-style interfaces. ...

  • Swagger UI
    Swagger UI

    Swagger UI is a dependency-free collection of HTML, Javascript, and CSS assets that dynamically generate beautiful documentation and sandbox from a Swagger-compliant API ...

  • Graphene
    Graphene

    Graphene is a Python library for building GraphQL schemas/types fast and easily. ...

  • Spring Boot
    Spring Boot

    Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration. ...

  • Laravel
    Laravel

    It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching. ...

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

Django REST framework alternatives & related posts

Django logo

Django

31.6K
28.6K
4K
The Web framework for perfectionists with deadlines
31.6K
28.6K
+ 1
4K
PROS OF DJANGO
  • 648
    Rapid development
  • 477
    Open source
  • 410
    Great community
  • 363
    Easy to learn
  • 269
    Mvc
  • 220
    Beautiful code
  • 214
    Elegant
  • 197
    Free
  • 195
    Great packages
  • 183
    Great libraries
  • 72
    Restful
  • 70
    Comes with auth and crud admin panel
  • 70
    Powerful
  • 66
    Great documentation
  • 62
    Great for web
  • 49
    Python
  • 38
    Great orm
  • 36
    Great for api
  • 28
    All included
  • 24
    Fast
  • 23
    Web Apps
  • 20
    Used by top startups
  • 19
    Clean
  • 18
    Easy setup
  • 17
    Sexy
  • 14
    Convention over configuration
  • 13
    ORM
  • 12
    Allows for very rapid development with great libraries
  • 11
    The Django community
  • 9
    King of backend world
  • 8
    Great MVC and templating engine
  • 7
    Its elegant and practical
  • 7
    Batteries included
  • 7
    Full stack
  • 6
    Fast prototyping
  • 6
    Cross-Platform
  • 6
    Have not found anything that it can't do
  • 6
    Mvt
  • 5
    Easy to develop end to end AI Models
  • 5
    Easy Structure , useful inbuilt library
  • 5
    Very quick to get something up and running
  • 4
    Easy
  • 4
    Great peformance
  • 4
    Many libraries
  • 4
    Python community
  • 4
    Modular
  • 4
    Map
  • 4
    Easy to change database manager
  • 4
    Zero code burden to change databases
  • 4
    Easy to use
  • 3
    Full-Text Search
  • 3
    Scaffold
  • 3
    Just the right level of abstraction
  • 1
    Node js
  • 1
    Scalable
  • 0
    Rails
  • 0
    Fastapi
CONS OF DJANGO
  • 25
    Underpowered templating
  • 22
    Autoreload restarts whole server
  • 21
    Underpowered ORM
  • 15
    URL dispatcher ignores HTTP method
  • 10
    Internal subcomponents coupling
  • 8
    Not nodejs
  • 7
    Admin
  • 7
    Configuration hell
  • 5
    Not as clean and nice documentation like Laravel
  • 3
    Bloated admin panel included
  • 3
    Python
  • 3
    Not typed
  • 2
    InEffective Multithreading
  • 2
    Overwhelming folder structure

related Django posts

Dmitry Mukhin

Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

See more

Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?

See more
Flask logo

Flask

16.5K
14.2K
1.6K
A microframework for Python based on Werkzeug, Jinja 2 and good intentions
16.5K
14.2K
+ 1
1.6K
PROS OF FLASK
  • 317
    Lightweight
  • 273
    Python
  • 216
    Minimal
  • 148
    Open source
  • 100
    Documentation
  • 68
    Easy to use
  • 55
    Easy to setup and get it going
  • 54
    Well designed
  • 50
    Easy to develop and maintain applications
  • 47
    Easy to get started
  • 21
    Beautiful code
  • 19
    Rapid development
  • 16
    Powerful
  • 15
    Expressive
  • 14
    Flexibilty
  • 13
    Simple to use
  • 13
    Awesome
  • 13
    Customizable
  • 12
    Speed
  • 12
    Love it
  • 12
    Get started quickly
  • 11
    Easy to integrate
  • 10
    Perfect for small to large projects with superb docs.
  • 10
    For it flexibility
  • 9
    Productive
  • 9
    Flexibilty and easy to use
  • 8
    Flask
  • 7
    User friendly
  • 7
    Not JS
  • 6
    Secured
  • 5
    Unopinionated
  • 2
    Secure
  • 2
    Orm
CONS OF FLASK
  • 10
    Not JS
  • 7
    Context
  • 5
    Not fast
  • 1
    Don't has many module as in spring

related Flask posts

James Man
Software Engineer at Pinterest · | 44 upvotes · 1M views
Shared insights
on
FlaskFlaskReactReact
at

One of our top priorities at Pinterest is fostering a safe and trustworthy experience for all Pinners. As Pinterest’s user base and ads business grow, the review volume has been increasing exponentially, and more content types require moderation support. To solve greater engineering and operational challenges at scale, we needed a highly-reliable and performant system to detect, report, evaluate, and act on abusive content and users and so we created Pinqueue.

Pinqueue-3.0 serves as a generic platform for content moderation and human labeling. Under the hood, Pinqueue3.0 is a Flask + React app powered by Pinterest’s very own Gestalt UI framework. On the backend, Pinqueue3.0 heavily relies on PinLater, a Pinterest-built reliable asynchronous job execution system, to handle the requests for enqueueing and action-taking. Using PinLater has significantly strengthened Pinqueue3.0’s overall infra with its capability of processing a massive load of events with configurable retry policies.

Hundreds of millions of people around the world use Pinterest to discover and do what they love, and our job is to protect them from abusive and harmful content. We’re committed to providing an inspirational yet safe experience to all Pinners. Solving trust & safety problems is a joint effort requiring expertise across multiple domains. Pinqueue3.0 not only plays a critical role in responsively taking down unsafe content, it also has become an enabler for future ML/automation initiatives by providing high-quality human labels. Going forward, we will continue to improve the review experience, measure review quality and collaborate with our machine learning teams to solve content moderation beyond manual reviews at an even larger scale.

See more

Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?

See more
Tastypie logo

Tastypie

35
50
4
Creating delicious APIs for Django apps since 2010.
35
50
+ 1
4
PROS OF TASTYPIE
  • 2
    Good in Django
  • 1
    Fast development
  • 1
    Customizable
CONS OF TASTYPIE
    Be the first to leave a con

    related Tastypie posts

    Swagger UI logo

    Swagger UI

    1.7K
    1.6K
    204
    A Collection of HTML, Javascript, and CSS assets that dynamically generate beautiful documentation
    1.7K
    1.6K
    + 1
    204
    PROS OF SWAGGER UI
    • 47
      Open Source
    • 34
      Can execute api calls from the documentation
    • 29
      Free to use
    • 19
      Customizable
    • 14
      Easy to implement in .Net
    • 13
      Mature, clean spec
    • 11
      API Visualization
    • 9
      Coverage
    • 6
      Scaffolding
    • 6
      Easy to use
    • 5
      Vibrant and active community
    • 4
      Elegant
    • 3
      Adopted by tm forum api
    • 2
      Clear for React
    • 1
      Api
    • 1
      Can deploy API to AWS API Gateway and AWS Lambda
    CONS OF SWAGGER UI
    • 3
      Need to learn YAML and RAML
    • 2
      Documentation doesn't look that good
    • 1
      Doesn't generate code snippets in different languages
    • 1
      You don’t actually get in-line error highlighting
    • 1
      Does not support hypermedia

    related Swagger UI posts

    Noah Zoschke
    Engineering Manager at Segment · | 30 upvotes · 2.3M views

    We just launched the Segment Config API (try it out for yourself here) — a set of public REST APIs that enable you to manage your Segment configuration. A public API is only as good as its #documentation. For the API reference doc we are using Postman.

    Postman is an “API development environment”. You download the desktop app, and build API requests by URL and payload. Over time you can build up a set of requests and organize them into a “Postman Collection”. You can generalize a collection with “collection variables”. This allows you to parameterize things like username, password and workspace_name so a user can fill their own values in before making an API call. This makes it possible to use Postman for one-off API tasks instead of writing code.

    Then you can add Markdown content to the entire collection, a folder of related methods, and/or every API method to explain how the APIs work. You can publish a collection and easily share it with a URL.

    This turns Postman from a personal #API utility to full-blown public interactive API documentation. The result is a great looking web page with all the API calls, docs and sample requests and responses in one place. Check out the results here.

    Postman’s powers don’t end here. You can automate Postman with “test scripts” and have it periodically run a collection scripts as “monitors”. We now have #QA around all the APIs in public docs to make sure they are always correct

    Along the way we tried other techniques for documenting APIs like ReadMe.io or Swagger UI. These required a lot of effort to customize.

    Writing and maintaining a Postman collection takes some work, but the resulting documentation site, interactivity and API testing tools are well worth it.

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

    Our whole Node.js backend stack consists of the following tools:

    • Lerna as a tool for multi package and multi repository management
    • npm as package manager
    • NestJS as Node.js framework
    • TypeScript as programming language
    • ExpressJS as web server
    • Swagger UI for visualizing and interacting with the API’s resources
    • Postman as a tool for API development
    • TypeORM as object relational mapping layer
    • JSON Web Token for access token management

    The main reason we have chosen Node.js over PHP is related to the following artifacts:

    • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
    • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
    • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
    • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
    See more
    Graphene logo

    Graphene

    96
    135
    0
    GraphQL framework for Python
    96
    135
    + 1
    0
    PROS OF GRAPHENE
    • 0
      Will replace RESTful interfaces
    • 0
      The future of API's
    CONS OF GRAPHENE
      Be the first to leave a con

      related Graphene posts

      Malthe Jørgensen

      We recently switched from MongoDB and the Python library MongoEngine to PostgreSQL and Django in order to:

      • Better leverage GraphQL (using the Graphene library)
      • Allow us to use the autogenerated Django admin interface
      • Allow better performance due to the way some of our pages present data
      • Give us more a mature stack in the form of Django replacing MongoEngine, which we had some issues with in the past.

      MongoDB was hosted on mlab, and we now host Postgres on Amazon RDS .

      See more
      Michael Mota
      Founder at AlterEstate · | 6 upvotes · 72.7K views

      We recently implemented GraphQL because we needed to build dynamic reports based on the user preference and configuration, this was extremely complicated with our actual RESTful API, the code started to get harder to maintain but switching to GraphQL helped us to to build beautiful reports for our clients that truly help them make data-driven decisions.

      Our goal is to implemented GraphQL in the whole platform eventually, we are using Graphene , a python library for Django .

      See more
      Spring Boot logo

      Spring Boot

      20.9K
      18.8K
      993
      Create Spring-powered, production-grade applications and services with absolute minimum fuss
      20.9K
      18.8K
      + 1
      993
      PROS OF SPRING BOOT
      • 140
        Powerful and handy
      • 132
        Easy setup
      • 123
        Java
      • 90
        Spring
      • 85
        Fast
      • 46
        Extensible
      • 37
        Lots of "off the shelf" functionalities
      • 32
        Cloud Solid
      • 26
        Caches well
      • 24
        Many receipes around for obscure features
      • 24
        Productive
      • 23
        Modular
      • 23
        Integrations with most other Java frameworks
      • 22
        Spring ecosystem is great
      • 21
        Fast Performance With Microservices
      • 20
        Auto-configuration
      • 18
        Community
      • 17
        Easy setup, Community Support, Solid for ERP apps
      • 15
        One-stop shop
      • 14
        Cross-platform
      • 14
        Easy to parallelize
      • 13
        Powerful 3rd party libraries and frameworks
      • 13
        Easy setup, good for build erp systems, well documented
      • 12
        Easy setup, Git Integration
      • 5
        It's so easier to start a project on spring
      • 4
        Kotlin
      CONS OF SPRING BOOT
      • 23
        Heavy weight
      • 17
        Annotation ceremony
      • 12
        Java
      • 11
        Many config files needed
      • 5
        Reactive
      • 4
        Excellent tools for cloud hosting, since 5.x

      related Spring Boot posts

      Praveen Mooli
      Engineering Manager at Taylor and Francis · | 17 upvotes · 2.5M views

      We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

      To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

      To build #Webapps we decided to use Angular 2 with RxJS

      #Devops - GitHub , Travis CI , Terraform , Docker , Serverless

      See more

      Is learning Spring and Spring Boot for web apps back-end development is still relevant in 2021? Feel free to share your views with comparison to Django/Node.js/ ExpressJS or other frameworks.

      Please share some good beginner resources to start learning about spring/spring boot framework to build the web apps.

      See more
      Laravel logo

      Laravel

      23.6K
      19.5K
      3.7K
      A PHP Framework For Web Artisans
      23.6K
      19.5K
      + 1
      3.7K
      PROS OF LARAVEL
      • 532
        Clean architecture
      • 380
        Growing community
      • 359
        Composer friendly
      • 329
        Open source
      • 310
        The only framework to consider for php
      • 212
        Mvc
      • 204
        Quickly develop
      • 162
        Dependency injection
      • 151
        Application architecture
      • 139
        Embraces good community packages
      • 68
        Write less, do more
      • 63
        Orm (eloquent)
      • 61
        Restful routing
      • 51
        Database migrations & seeds
      • 50
        Artisan scaffolding and migrations
      • 36
        Awesome
      • 36
        Great documentation
      • 27
        Awsome, Powerfull, Fast and Rapid
      • 26
        Build Apps faster, easier and better
      • 25
        Promotes elegant coding
      • 22
        JSON friendly
      • 22
        Modern PHP
      • 22
        Easy to learn, scalability
      • 22
        Eloquent ORM
      • 21
        Most easy for me
      • 21
        Blade Template
      • 20
        Test-Driven
      • 20
        Beautiful
      • 14
        Based on SOLID
      • 14
        Security
      • 12
        Easy to attach Middleware
      • 12
        Cool
      • 12
        Clean Documentation
      • 11
        Simple
      • 11
        Convention over Configuration
      • 10
        Easy Request Validatin
      • 9
        Easy to use
      • 9
        Fast
      • 9
        Simpler
      • 8
        Its just wow
      • 8
        Laravel + Cassandra = Killer Framework
      • 8
        Get going quickly straight out of the box. BYOKDM
      • 8
        Friendly API
      • 7
        Simplistic , easy and faster
      • 7
        Super easy and powerful
      • 7
        Less dependencies
      • 6
        Its beautiful to code in
      • 6
        Great customer support
      • 5
        Minimum system requirements
      • 5
        Laravel Mix
      • 5
        Php7
      • 5
        Speed
      • 5
        Easy
      • 5
        The only "cons" is wrong! No static method just Facades
      • 5
        Fast and Clarify framework
      • 5
        Active Record
      • 4
        Laragon
      • 4
        Composer
      • 4
        Easy views handling and great ORM
      • 4
        Eloquent
      • 3
        Laravel Nova
      • 3
        Intuitive usage
      • 3
        Ease of use
      • 3
        Cashier with Braintree and Stripe
      • 3
        Laravel Forge and Envoy
      • 3
        Laravel Horizon and Telescope
      • 3
        Laravel Passport
      • 3
        Laravel casher
      • 3
        Laravel Spark
      • 2
        Scout
      • 2
        Rapid development
      • 1
        Succint sintax
      • 1
        Deployment
      CONS OF LARAVEL
      • 48
        PHP
      • 31
        Too many dependency
      • 22
        Slower than the other two
      • 17
        A lot of static method calls for convenience
      • 15
        Too many include
      • 12
        Heavy
      • 8
        Bloated
      • 7
        Laravel
      • 6
        Confusing
      • 5
        Too underrated
      • 3
        Not fast with MongoDB
      • 1
        Difficult to learn
      • 1
        Not using SOLID principles

      related Laravel posts

      I need to build a web application plus android and IOS apps for an enterprise, like an e-commerce portal. It will have intensive use of MySQL to display thousands (40-50k) of live product information in an interactive table (searchable, filterable), live delivery tracking. It has to be secure, as it will handle information on customers, sales, inventory. Here is the technology stack: Backend: Laravel 7 Frondend: Vue.js, React or AngularJS?

      Need help deciding technology stack. Thanks.

      See more
      Antonio Sanchez

      Back at the start of 2017, we decided to create a web-based tool for the SEO OnPage analysis of our clients' websites. We had over 2.000 websites to analyze, so we had to perform thousands of requests to get every single page from those websites, process the information and save the big amounts of data somewhere.

      Very soon we realized that the initial chosen script language and database, PHP, Laravel and MySQL, was not going to be able to cope efficiently with such a task.

      By that time, we were doing some experiments for other projects with a language we had recently get to know, Go , so we decided to get a try and code the crawler using it. It was fantastic, we could process much more data with way less CPU power and in less time. By using the concurrency abilites that the language has to offers, we could also do more Http requests in less time.

      Unfortunately, I have no comparison numbers to show about the performance differences between Go and PHP since the difference was so clear from the beginning and that we didn't feel the need to do further comparison tests nor document it. We just switched fully to Go.

      There was still a problem: despite the big amount of Data we were generating, MySQL was performing very well, but as we were adding more and more features to the software and with those features more and more different type of data to save, it was a nightmare for the database architects to structure everything correctly on the database, so it was clear what we had to do next: switch to a NoSQL database. So we switched to MongoDB, and it was also fantastic: we were expending almost zero time in thinking how to structure the Database and the performance also seemed to be better, but again, I have no comparison numbers to show due to the lack of time.

      We also decided to switch the website from PHP and Laravel to JavaScript and Node.js and ExpressJS since working with the JSON Data that we were saving now in the Database would be easier.

      As of now, we don't only use the tool intern but we also opened it for everyone to use for free: https://tool-seo.com

      See more
      Firebase logo

      Firebase

      33.8K
      29.3K
      1.9K
      The Realtime App Platform
      33.8K
      29.3K
      + 1
      1.9K
      PROS OF FIREBASE
      • 369
        Realtime backend made easy
      • 268
        Fast and responsive
      • 240
        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
        Firebase hosting
      • 6
        Awesome next-gen backend
      • 6
        Ios adaptor
      • 6
        Built in user auth/oauth
      • 4
        Speed of light
      • 4
        Very easy to use
      • 3
        Great
      • 3
        Brilliant for startups
      • 3
        It's made development super fast
      • 2
        Push notification
      • 2
        Free hosting
      • 2
        Free authentication solution
      • 2
        Cloud functions
      • 2
        JS Offline and Sync suport
      • 2
        Low battery consumption
      • 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 to use
      • 1
        Easy Reactjs integration
      • 1
        Free SSL
      • 1
        Faster workflow
      • 1
        Google's support
      • 1
        Simple and easy
      • 1
        CDN & cache out of the box
      • 1
        Large
      • 1
        .net
      • 1
        Serverless
      • 1
        Good Free Limits
      CONS OF FIREBASE
      • 31
        Can become expensive
      • 15
        Scalability is not infinite
      • 15
        No open source, you depend on external company
      • 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

      Stephen Gheysens
      Senior Solutions Engineer at Twilio · | 14 upvotes · 892.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