Alternatives to Django logo

Alternatives to Django

Flask, Node.js, Rails, Laravel, and PHP are the most popular alternatives and competitors to Django.
37K
33.5K
+ 1
4.2K

What is Django and what are its top alternatives?

Django is a high-level web framework written in Python that encourages rapid development and clean, pragmatic design. It follows the model-template-views architectural pattern and includes built-in features like an ORM system, authentication support, and a customizable admin interface. However, Django has a steep learning curve for beginners due to its comprehensive feature set and may be perceived as overly complex for smaller projects.

  1. Flask: Flask is a lightweight web framework in Python that is simple and easy to use. It provides flexibility and extensibility, making it ideal for small to medium-sized projects. However, Flask lacks some built-in features like an ORM system and an admin interface compared to Django.

  2. Ruby on Rails: Ruby on Rails is a web framework written in Ruby that follows the convention over configuration principle. It emphasizes developer productivity and includes features like migrations, scaffolding, and a standardized directory structure. Despite its high performance and robustness, Rails may have a steeper learning curve for beginners than Django.

  3. Express.js: Express.js is a minimal and flexible web application framework for Node.js. It provides a thin layer of fundamental web application features and allows developers to build APIs quickly. However, Express.js may require more manual configuration and lacks some built-in features compared to Django.

  4. Spring Boot: Spring Boot is a Java-based framework that simplifies the development of production-ready applications. It offers a wide range of features like auto-configuration, embedded servers, and robust security. Spring Boot provides a strong ecosystem and scalability but may have a higher complexity compared to Django.

  5. Laravel: Laravel is a PHP framework that prioritizes developer experience and expressive code syntax. It includes features like Eloquent ORM, Blade templating engine, and Artisan command-line interface. Laravel is known for its elegant syntax and developer-friendly tools, but it may have a slower performance compared to Django.

  6. FastAPI: FastAPI is a modern web framework for building APIs with Python. It offers high performance through asynchronous programming and automatic generation of OpenAPI documentation. FastAPI is easy to use and efficient, but it may have a smaller community and ecosystem compared to Django.

  7. Vue.js: Vue.js is a progressive JavaScript framework for building user interfaces. It provides reactive data binding and component-based architecture, making it easy to integrate with other libraries or projects. Vue.js offers simplicity and flexibility but may require additional libraries for server-side features compared to Django.

  8. Angular: Angular is a robust frontend framework developed by Google that enables the building of dynamic web applications. It includes features like two-way data binding, dependency injection, and observables for handling asynchronous operations. Angular has a steep learning curve and may have a heavier footprint compared to Django.

  9. ASP.NET Core: ASP.NET Core is a cross-platform, high-performance framework for building modern, cloud-based, internet-connected applications. It provides features like Razor Pages, Entity Framework, and built-in authentication. ASP.NET Core offers scalability and security but may have a higher complexity compared to Django.

  10. NestJS: NestJS is a progressive Node.js framework for building efficient, reliable, and scalable server-side applications. It follows an Angular-inspired structure and offers features like dependency injection, middleware support, and GraphQL integration. NestJS provides a high level of abstraction and scalability but may have a steeper learning curve compared to Django.

Top Alternatives to Django

  • Flask
    Flask

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

  • Node.js
    Node.js

    Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. ...

  • Rails
    Rails

    Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern. ...

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

  • PHP
    PHP

    Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world. ...

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

  • Drupal
    Drupal

    Drupal is an open source content management platform powering millions of websites and applications. It’s built, used, and supported by an active and diverse community of people around the world. ...

  • ExpressJS
    ExpressJS

    Express is a minimal and flexible node.js web application framework, providing a robust set of features for building single and multi-page, and hybrid web applications. ...

Django alternatives & related posts

Flask logo

Flask

18.8K
15.8K
82
A microframework for Python based on Werkzeug, Jinja 2 and good intentions
18.8K
15.8K
+ 1
82
PROS OF FLASK
  • 14
    Flexibilty
  • 10
    For it flexibility
  • 9
    Flexibilty and easy to use
  • 8
    Flask
  • 7
    User friendly
  • 6
    Secured
  • 5
    Unopinionated
  • 3
    Orm
  • 2
    Secure
  • 1
    Beautiful code
  • 1
    Easy to get started
  • 1
    Easy to develop and maintain applications
  • 1
    Not JS
  • 1
    Easy to use
  • 1
    Documentation
  • 1
    Python
  • 1
    Minimal
  • 1
    Lightweight
  • 1
    Easy to setup and get it going
  • 1
    Perfect for small to large projects with superb docs.
  • 1
    Easy to integrate
  • 1
    Speed
  • 1
    Get started quickly
  • 1
    Customizable
  • 1
    Simple to use
  • 1
    Powerful
  • 1
    Rapid development
  • 0
    Open source
  • 0
    Well designed
  • 0
    Productive
  • 0
    Awesome
  • 0
    Expressive
  • 0
    Love it
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 · | 46 upvotes · 2.8M 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
Node.js logo

Node.js

184.5K
156.6K
8.5K
A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
184.5K
156.6K
+ 1
8.5K
PROS OF NODE.JS
  • 1.4K
    Npm
  • 1.3K
    Javascript
  • 1.1K
    Great libraries
  • 1K
    High-performance
  • 805
    Open source
  • 486
    Great for apis
  • 477
    Asynchronous
  • 423
    Great community
  • 390
    Great for realtime apps
  • 296
    Great for command line utilities
  • 84
    Websockets
  • 83
    Node Modules
  • 69
    Uber Simple
  • 59
    Great modularity
  • 58
    Allows us to reuse code in the frontend
  • 42
    Easy to start
  • 35
    Great for Data Streaming
  • 32
    Realtime
  • 28
    Awesome
  • 25
    Non blocking IO
  • 18
    Can be used as a proxy
  • 17
    High performance, open source, scalable
  • 16
    Non-blocking and modular
  • 15
    Easy and Fun
  • 14
    Easy and powerful
  • 13
    Future of BackEnd
  • 13
    Same lang as AngularJS
  • 12
    Fullstack
  • 11
    Fast
  • 10
    Scalability
  • 10
    Cross platform
  • 9
    Simple
  • 8
    Mean Stack
  • 7
    Great for webapps
  • 7
    Easy concurrency
  • 6
    Typescript
  • 6
    Fast, simple code and async
  • 6
    React
  • 6
    Friendly
  • 5
    Control everything
  • 5
    Its amazingly fast and scalable
  • 5
    Easy to use and fast and goes well with JSONdb's
  • 5
    Scalable
  • 5
    Great speed
  • 5
    Fast development
  • 4
    It's fast
  • 4
    Easy to use
  • 4
    Isomorphic coolness
  • 3
    Great community
  • 3
    Not Python
  • 3
    Sooper easy for the Backend connectivity
  • 3
    TypeScript Support
  • 3
    Blazing fast
  • 3
    Performant and fast prototyping
  • 3
    Easy to learn
  • 3
    Easy
  • 3
    Scales, fast, simple, great community, npm, express
  • 3
    One language, end-to-end
  • 3
    Less boilerplate code
  • 2
    Npm i ape-updating
  • 2
    Event Driven
  • 2
    Lovely
  • 1
    Creat for apis
  • 0
    Node
CONS OF NODE.JS
  • 46
    Bound to a single CPU
  • 45
    New framework every day
  • 40
    Lots of terrible examples on the internet
  • 33
    Asynchronous programming is the worst
  • 24
    Callback
  • 19
    Javascript
  • 11
    Dependency based on GitHub
  • 11
    Dependency hell
  • 10
    Low computational power
  • 7
    Can block whole server easily
  • 7
    Callback functions may not fire on expected sequence
  • 7
    Very very Slow
  • 4
    Breaking updates
  • 4
    Unstable
  • 3
    No standard approach
  • 3
    Unneeded over complication
  • 1
    Can't read server session
  • 1
    Bad transitive dependency management

related Node.js posts

Shared insights
on
Node.jsNode.jsGraphQLGraphQLMongoDBMongoDB

I just finished the very first version of my new hobby project: #MovieGeeks. It is a minimalist online movie catalog for you to save the movies you want to see and for rating the movies you already saw. This is just the beginning as I am planning to add more features on the lines of sharing and discovery

For the #BackEnd I decided to use Node.js , GraphQL and MongoDB:

  1. Node.js has a huge community so it will always be a safe choice in terms of libraries and finding solutions to problems you may have

  2. GraphQL because I needed to improve my skills with it and because I was never comfortable with the usual REST approach. I believe GraphQL is a better option as it feels more natural to write apis, it improves the development velocity, by definition it fixes the over-fetching and under-fetching problem that is so common on REST apis, and on top of that, the community is getting bigger and bigger.

  3. MongoDB was my choice for the database as I already have a lot of experience working on it and because, despite of some bad reputation it has acquired in the last months, I still believe it is a powerful database for at least a very long list of use cases such as the one I needed for my website

See more
Nick Rockwell
SVP, Engineering at Fastly · | 46 upvotes · 3.4M views

When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

See more
Rails logo

Rails

19.2K
13.5K
5.4K
Web development that doesn't hurt
19.2K
13.5K
+ 1
5.4K
PROS OF RAILS
  • 856
    Rapid development
  • 652
    Great gems
  • 606
    Great community
  • 484
    Convention over configuration
  • 417
    Mvc
  • 348
    Great for web
  • 343
    Beautiful code
  • 310
    Open source
  • 270
    Great libraries
  • 261
    Active record
  • 108
    Elegant
  • 90
    Easy to learn
  • 88
    Easy Database Migrations
  • 82
    Makes you happy
  • 75
    Free
  • 62
    Great routing
  • 54
    Has everything you need to get the job done
  • 41
    Great Data Modeling
  • 38
    MVC - Easy to start on
  • 38
    Beautiful
  • 35
    Easy setup
  • 26
    Great caching
  • 25
    Ultra rapid development time
  • 22
    It's super easy
  • 17
    Great Resources
  • 16
    Easy to build mockups that work
  • 14
    Less Boilerplate
  • 7
    Developer Friendly
  • 7
    API Development
  • 6
    Great documentation
  • 5
    Easy REST API creation
  • 5
    Quick
  • 4
    Intuitive
  • 4
    Great language
  • 4
    Haml and sass
  • 4
    Easy to learn, use, improvise and update
  • 2
    Metaprogramming
  • 2
    It works
  • 2
    Jet packs come standard
  • 2
    Easy and fast
  • 2
    Legacy
  • 1
    It's intuitive
  • 1
    Convention over configuration
  • 1
    Easy Testing
  • 1
    Cancan
CONS OF RAILS
  • 24
    Too much "magic" (hidden behavior)
  • 14
    Poor raw performance
  • 12
    Asset system is too primitive and outdated
  • 6
    Heavy use of mixins
  • 6
    Bloat in models
  • 4
    Very Very slow

related Rails posts

Zach Holman

Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

See more
Russel Werner
Lead Engineer at StackShare · | 32 upvotes · 2.2M 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
Laravel logo

Laravel

27.5K
22.9K
3.9K
A PHP Framework For Web Artisans
27.5K
22.9K
+ 1
3.9K
PROS OF LARAVEL
  • 553
    Clean architecture
  • 392
    Growing community
  • 370
    Composer friendly
  • 344
    Open source
  • 324
    The only framework to consider for php
  • 220
    Mvc
  • 210
    Quickly develop
  • 168
    Dependency injection
  • 156
    Application architecture
  • 143
    Embraces good community packages
  • 73
    Write less, do more
  • 71
    Orm (eloquent)
  • 66
    Restful routing
  • 57
    Database migrations & seeds
  • 55
    Artisan scaffolding and migrations
  • 41
    Great documentation
  • 40
    Awesome
  • 30
    Awsome, Powerfull, Fast and Rapid
  • 29
    Build Apps faster, easier and better
  • 28
    Eloquent ORM
  • 26
    Promotes elegant coding
  • 26
    Modern PHP
  • 26
    JSON friendly
  • 25
    Most easy for me
  • 24
    Easy to learn, scalability
  • 23
    Beautiful
  • 22
    Blade Template
  • 21
    Test-Driven
  • 15
    Security
  • 15
    Based on SOLID
  • 13
    Clean Documentation
  • 13
    Easy to attach Middleware
  • 13
    Cool
  • 12
    Simple
  • 12
    Convention over Configuration
  • 11
    Easy Request Validatin
  • 10
    Simpler
  • 10
    Fast
  • 10
    Easy to use
  • 9
    Get going quickly straight out of the box. BYOKDM
  • 9
    Its just wow
  • 8
    Laravel + Cassandra = Killer Framework
  • 8
    Simplistic , easy and faster
  • 8
    Friendly API
  • 7
    Less dependencies
  • 7
    Super easy and powerful
  • 6
    Great customer support
  • 6
    Its beautiful to code in
  • 5
    Speed
  • 5
    Eloquent
  • 5
    Composer
  • 5
    Minimum system requirements
  • 5
    Laravel Mix
  • 5
    Easy
  • 5
    The only "cons" is wrong! No static method just Facades
  • 5
    Fast and Clarify framework
  • 5
    Active Record
  • 5
    Php7
  • 4
    Ease of use
  • 4
    Laragon
  • 4
    Laravel casher
  • 4
    Easy views handling and great ORM
  • 4
    Laravel Forge and Envoy
  • 4
    Cashier with Braintree and Stripe
  • 3
    Laravel Passport
  • 3
    Laravel Spark
  • 3
    Intuitive usage
  • 3
    Laravel Horizon and Telescope
  • 3
    Laravel Nova
  • 3
    Rapid development
  • 2
    Laravel Vite
  • 2
    Scout
  • 2
    Deployment
  • 1
    Succint sintax
CONS OF LARAVEL
  • 54
    PHP
  • 33
    Too many dependency
  • 23
    Slower than the other two
  • 17
    A lot of static method calls for convenience
  • 15
    Too many include
  • 13
    Heavy
  • 9
    Bloated
  • 8
    Laravel
  • 7
    Confusing
  • 5
    Too underrated
  • 4
    Not fast with MongoDB
  • 1
    Slow and too much big
  • 1
    Not using SOLID principles
  • 1
    Difficult to learn

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
David Watson
at Realtime App Solutions · | 15 upvotes · 98.7K views

Coming from a non-web development environment background, I was a bit lost a first and bewildered by all the varying tools and platforms, and spent much too long evaluating before eventualy deciding on Laravel as the main core of my development.

But as I started development with Laravel that lead me into discovering Vue.js for creating beautiful front-end components that were easy to configure and extend, so I decided to standardise on Vue.js for most of my front-end development.

During my search for additional Vue.js components, a chance comment in a @laravel forum , led me to discover Quasar Framework initially for it's wide range of in-built components ... but once, I realised that Quasar Framework allowed me to use the same codebase to create apps for SPA, PWA, iOS, Android, and Electron then I was hooked.

So, I'm now using mainly just Quasar Framework for all the front-end, with Laravel providing a backend API service to the Front-end apps.

I'm deploying this all to DigitalOcean droplets via service called Moss.sh which deploys my private GitHub repositories directly to DigitalOcean in realtime.

See more
PHP logo

PHP

142.6K
79.7K
4.6K
A popular general-purpose scripting language that is especially suited to web development
142.6K
79.7K
+ 1
4.6K
PROS OF PHP
  • 951
    Large community
  • 817
    Open source
  • 766
    Easy deployment
  • 487
    Great frameworks
  • 387
    The best glue on the web
  • 235
    Continual improvements
  • 185
    Good old web
  • 145
    Web foundation
  • 135
    Community packages
  • 125
    Tool support
  • 35
    Used by wordpress
  • 34
    Excellent documentation
  • 29
    Used by Facebook
  • 23
    Because of Symfony
  • 21
    Dynamic Language
  • 17
    Cheap hosting
  • 16
    Easy to learn
  • 14
    Awesome Language and easy to implement
  • 14
    Very powerful web language
  • 14
    Fast development
  • 13
    Composer
  • 12
    Flexibility, syntax, extensibility
  • 12
    Because of Laravel
  • 9
    Easiest deployment
  • 8
    Readable Code
  • 8
    Fast
  • 7
    Most of the web uses it
  • 7
    Worst popularity quality ratio
  • 7
    Short development lead times
  • 7
    Fastestest Time to Version 1.0 Deployments
  • 6
    Faster then ever
  • 5
    Open source and large community
  • 5
    Simple, flexible yet Scalable
  • 4
    I have no choice :(
  • 4
    Has the best ecommerce(Magento,Prestashop,Opencart,etc)
  • 4
    Is like one zip of air
  • 4
    Open source and great framework
  • 4
    Large community, easy setup, easy deployment, framework
  • 4
    Great developer experience
  • 4
    Easy to use and learn
  • 4
    Cheap to own
  • 4
    Easy to learn, a big community, lot of frameworks
  • 2
    Walk away
  • 2
    Used by STOMT
  • 2
    Hard not to use
  • 2
    Fault tolerance
  • 2
    Great flexibility. From fast prototyping to large apps
  • 2
    Interpreted at the run time
  • 2
    FFI
  • 2
    Safe the planet
  • 1
    It can get you a lamborghini
  • 1
    Secure
  • 1
    Simplesaml
  • 1
    Bando
  • 0
    Secure
CONS OF PHP
  • 22
    So easy to learn, good practices are hard to find
  • 16
    Inconsistent API
  • 8
    Fragmented community
  • 6
    Not secure
  • 3
    No routing system
  • 3
    Hard to debug
  • 2
    Old

related PHP posts

Nick Rockwell
SVP, Engineering at Fastly · | 46 upvotes · 3.4M views

When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 27 upvotes · 4.8M 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
WordPress logo

WordPress

96.2K
38.7K
2.1K
A semantic personal publishing platform with a focus on aesthetics, web standards, and usability.
96.2K
38.7K
+ 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.5M 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 · 55.8K 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
Drupal logo

Drupal

10.8K
3.8K
359
Free, Open, Modular CMS written in PHP
10.8K
3.8K
+ 1
359
PROS OF DRUPAL
  • 75
    Stable, highly functional cms
  • 60
    Great community
  • 44
    Easy cms to make websites
  • 43
    Highly customizable
  • 22
    Digital customer experience delivery platform
  • 17
    Really powerful
  • 16
    Customizable
  • 11
    Flexible
  • 10
    Good tool for prototyping
  • 9
    Enterprise proven over many years when others failed
  • 8
    Headless adds even more power/flexibility
  • 8
    Open source
  • 7
    Each version becomes more intuitive for clients to use
  • 7
    Well documented
  • 6
    Lego blocks methodology
  • 4
    Caching and performance
  • 3
    Powerful
  • 3
    Built on Symfony
  • 3
    Can build anything
  • 2
    Views
  • 1
    API-based CMS
CONS OF DRUPAL
  • 1
    Steep learning curve
  • 1
    DJango

related Drupal posts

Hi, I am working as a web developer (PHP, Laravel, AngularJS, and MySQL) with more than 8 years of experience and looking for a tech stack that pays better. I have a little bit of knowledge of Core Java. For better opportunities, Should I learn Java, Spring Boot or Python. Or should I learn Drupal, WordPress or Magento? Any guidance would be really appreciated! Thanks.

See more

Hi. I’m a lead developer in charge of designing the build for version 2.0 of our startup SaaS website which is currently a traditional Drupal 7 site. I’m just looking for some peer advice that I am headed down an ok path now the product has grown & changed. tl;dr; 1) Is building a decoupled/headless Drupal 10 site with a JavaScript framework a dumb idea? 2) Should I look to a different headless CMS? 3) React or Vue.js or (other) in 2022?

Our requirements for our new site include

  • White labeling / multisite spawning (will need separate databases for each)
  • Complex permissions and several user roles
  • Robust security
  • Mobile app capability for iOS (for now - Android in the future)
  • Multilingual capability
  • Easy user management/creation by non-devs
  • Reporting capabilities
  • Some basic “marketing” pages (but this could be separate from the web app I suppose)
  • A large amount of hosted video/image assets on AWS or similar
  • Weekly/daily CRON jobs to send out emails & reports

Being that I am experienced in Drupal & PHP, my thought was to build a headless site with a Vue.js or React as the front end in Drupal 10. I've only got minimal experience in either JS framework so I'm not sure which I should choose to skill up. Does this seem reasonable or am I barking up the wrong tree?

See more
ExpressJS logo

ExpressJS

31.4K
23.3K
1.6K
Sinatra inspired web development framework for node.js -- insanely fast, flexible, and simple
31.4K
23.3K
+ 1
1.6K
PROS OF EXPRESSJS
  • 380
    Simple
  • 336
    Node.js
  • 244
    Javascript
  • 193
    High performance
  • 152
    Robust routing
  • 73
    Middlewares
  • 71
    Open source
  • 59
    Great community
  • 37
    Hybrid web applications
  • 16
    Well documented
  • 9
    Rapid development
  • 9
    Sinatra inspired
  • 7
    Socket connection
  • 7
    Isomorphic js.. superfast and easy
  • 5
    Light weight
  • 4
    Resource available for learning
  • 4
    Npm
  • 3
    Event loop
  • 3
    Callbacks
  • 2
    Data stream
CONS OF EXPRESSJS
  • 27
    Not python
  • 17
    Overrated
  • 14
    No multithreading
  • 9
    Javascript
  • 5
    Not fast
  • 3
    Easily Insecure for Novices

related ExpressJS posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 27 upvotes · 4.8M 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

Repost

Overview: To put it simply, we plan to use the MERN stack to build our web application. MongoDB will be used as our primary database. We will use ExpressJS alongside Node.js to set up our API endpoints. Additionally, we plan to use React to build our SPA on the client side and use Redis on the server side as our primary caching solution. Initially, while working on the project, we plan to deploy our server and client both on Heroku . However, Heroku is very limited and we will need the benefits of an Infrastructure as a Service so we will use Amazon EC2 to later deploy our final version of the application.

Serverside: nodemon will allow us to automatically restart a running instance of our node app when files changes take place. We decided to use MongoDB because it is a non relational database which uses the Document Object Model. This allows a lot of flexibility as compared to a RDMS like SQL which requires a very structural model of data that does not change too much. Another strength of MongoDB is its ease in scalability. We will use Mongoose along side MongoDB to model our application data. Additionally, we will host our MongoDB cluster remotely on MongoDB Atlas. Bcrypt will be used to encrypt user passwords that will be stored in the DB. This is to avoid the risks of storing plain text passwords. Moreover, we will use Cloudinary to store images uploaded by the user. We will also use the Twilio SendGrid API to enable automated emails sent by our application. To protect private API endpoints, we will use JSON Web Token and Passport. Also, PayPal will be used as a payment gateway to accept payments from users.

Client Side: As mentioned earlier, we will use React to build our SPA. React uses a virtual DOM which is very efficient in rendering a page. Also React will allow us to reuse components. Furthermore, it is very popular and there is a large community that uses React so it can be helpful if we run into issues. We also plan to make a cross platform mobile application later and using React will allow us to reuse a lot of our code with React Native. Redux will be used to manage state. Redux works great with React and will help us manage a global state in the app and avoid the complications of each component having its own state. Additionally, we will use Bootstrap components and custom CSS to style our app.

Other: Git will be used for version control. During the later stages of our project, we will use Google Analytics to collect useful data regarding user interactions. Moreover, Slack will be our primary communication tool. Also, we will use Visual Studio Code as our primary code editor because it is very light weight and has a wide variety of extensions that will boost productivity. Postman will be used to interact with and debug our API endpoints.

See more