Alternatives to Django logo

Alternatives to Django

Flask, Node.js, Rails, Laravel, and PHP are the most popular alternatives and competitors to Django.
32.4K
29.4K
+ 1
4K

What is Django and what are its top alternatives?

Django is a high-level Python Web framework that encourages rapid development and clean, pragmatic design.
Django is a tool in the Frameworks (Full Stack) category of a tech stack.
Django is an open source tool with 67.4K GitHub stars and 28.2K GitHub forks. Here’s a link to Django's open source repository on GitHub

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

16.9K
14.6K
1.6K
A microframework for Python based on Werkzeug, Jinja 2 and good intentions
16.9K
14.6K
+ 1
1.6K
PROS OF FLASK
  • 319
    Lightweight
  • 275
    Python
  • 217
    Minimal
  • 149
    Open source
  • 100
    Documentation
  • 69
    Easy to use
  • 55
    Easy to setup and get it going
  • 55
    Well designed
  • 51
    Easy to develop and maintain applications
  • 48
    Easy to get started
  • 22
    Beautiful code
  • 19
    Rapid development
  • 16
    Powerful
  • 15
    Expressive
  • 14
    Customizable
  • 14
    Flexibilty
  • 14
    Simple to use
  • 13
    Get started quickly
  • 13
    Love it
  • 13
    Awesome
  • 12
    Speed
  • 11
    Easy to integrate
  • 11
    Perfect for small to large projects with superb docs.
  • 10
    For it flexibility
  • 9
    Flexibilty and easy to use
  • 9
    Productive
  • 8
    Flask
  • 8
    Not JS
  • 7
    User friendly
  • 6
    Secured
  • 5
    Unopinionated
  • 3
    Orm
  • 2
    Secure
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 · 1.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
Node.js logo

Node.js

154K
133.8K
8.5K
A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
154K
133.8K
+ 1
8.5K
PROS OF NODE.JS
  • 1.4K
    Npm
  • 1.3K
    Javascript
  • 1.1K
    Great libraries
  • 1K
    High-performance
  • 802
    Open source
  • 485
    Great for apis
  • 475
    Asynchronous
  • 420
    Great community
  • 390
    Great for realtime apps
  • 296
    Great for command line utilities
  • 82
    Websockets
  • 81
    Node Modules
  • 68
    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
    Same lang as AngularJS
  • 13
    Future of BackEnd
  • 12
    Fullstack
  • 11
    Fast
  • 10
    Scalability
  • 10
    Cross platform
  • 9
    Simple
  • 8
    Mean Stack
  • 7
    Easy concurrency
  • 7
    Great for webapps
  • 6
    Typescript
  • 6
    Fast, simple code and async
  • 6
    Friendly
  • 6
    React
  • 5
    Its amazingly fast and scalable
  • 5
    Scalable
  • 5
    Great speed
  • 5
    Control everything
  • 5
    Fast development
  • 5
    Easy to use and fast and goes well with JSONdb's
  • 4
    Easy to use
  • 4
    It's fast
  • 4
    Isomorphic coolness
  • 3
    Great community
  • 3
    Scales, fast, simple, great community, npm, express
  • 3
    TypeScript Support
  • 3
    Sooper easy for the Backend connectivity
  • 3
    Not Python
  • 3
    One language, end-to-end
  • 3
    Easy
  • 3
    Easy to learn
  • 3
    Less boilerplate code
  • 3
    Performant and fast prototyping
  • 3
    Blazing fast
  • 2
    Event Driven
  • 2
    Lovely
  • 2
    Npm i ape-updating
  • 1
    Creat for apis
  • 0
    Node
CONS OF NODE.JS
  • 46
    Bound to a single CPU
  • 43
    New framework every day
  • 37
    Lots of terrible examples on the internet
  • 31
    Asynchronous programming is the worst
  • 23
    Callback
  • 18
    Javascript
  • 11
    Dependency based on GitHub
  • 11
    Dependency hell
  • 10
    Low computational power
  • 7
    Very very Slow
  • 7
    Can block whole server easily
  • 6
    Callback functions may not fire on expected sequence
  • 3
    Unneeded over complication
  • 3
    Unstable
  • 3
    Breaking updates
  • 2
    No standard approach
  • 1
    Bad transitive dependency management
  • 1
    Can't read server session

related Node.js posts

Nick Rockwell
SVP, Engineering at Fastly · | 44 upvotes · 2.2M 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
Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 41 upvotes · 5.5M views

How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

https://eng.uber.com/distributed-tracing/

(GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

See more
Rails logo

Rails

17.3K
12.4K
5.4K
Web development that doesn't hurt
17.3K
12.4K
+ 1
5.4K
PROS OF RAILS
  • 852
    Rapid development
  • 651
    Great gems
  • 605
    Great community
  • 481
    Convention over configuration
  • 417
    Mvc
  • 349
    Great for web
  • 344
    Beautiful code
  • 311
    Open source
  • 270
    Great libraries
  • 260
    Active record
  • 106
    Elegant
  • 89
    Easy to learn
  • 87
    Easy Database Migrations
  • 79
    Makes you happy
  • 74
    Free
  • 62
    Great routing
  • 53
    Has everything you need to get the job done
  • 41
    Great Data Modeling
  • 38
    Beautiful
  • 38
    MVC - Easy to start on
  • 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
    Great language
  • 4
    Intuitive
  • 4
    Haml and sass
  • 4
    Easy to learn, use, improvise and update
  • 2
    It works
  • 2
    Metaprogramming
  • 2
    Legacy
  • 2
    Jet packs come standard
  • 2
    Easy and fast
  • 1
    Convention over configuration
  • 1
    Easy Testing
  • 1
    Cancan
  • 1
    It's intuitive
CONS OF RAILS
  • 22
    Too much "magic" (hidden behavior)
  • 14
    Poor raw performance
  • 11
    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 · 1.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
Laravel logo

Laravel

24.2K
20.1K
3.7K
A PHP Framework For Web Artisans
24.2K
20.1K
+ 1
3.7K
PROS OF LARAVEL
  • 533
    Clean architecture
  • 381
    Growing community
  • 359
    Composer friendly
  • 330
    Open source
  • 310
    The only framework to consider for php
  • 213
    Mvc
  • 204
    Quickly develop
  • 163
    Dependency injection
  • 151
    Application architecture
  • 139
    Embraces good community packages
  • 68
    Write less, do more
  • 64
    Orm (eloquent)
  • 62
    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
  • 23
    Eloquent ORM
  • 22
    Modern PHP
  • 22
    Easy to learn, scalability
  • 22
    JSON friendly
  • 21
    Blade Template
  • 21
    Most easy for me
  • 20
    Beautiful
  • 20
    Test-Driven
  • 14
    Security
  • 14
    Based on SOLID
  • 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
PHP logo

PHP

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

related PHP posts

Nick Rockwell
SVP, Engineering at Fastly · | 44 upvotes · 2.2M 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 · | 26 upvotes · 3.1M 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

90.1K
33.7K
2.1K
A semantic personal publishing platform with a focus on aesthetics, web standards, and usability.
90.1K
33.7K
+ 1
2.1K
PROS OF WORDPRESS
  • 412
    Customizable
  • 362
    Easy to manage
  • 351
    Plugins & themes
  • 258
    Non-tech colleagues can update website content
  • 246
    Really powerful
  • 144
    Rapid website development
  • 77
    Best documentation
  • 51
    Codex
  • 44
    Product feature set
  • 35
    Custom/internal social network
  • 16
    Open source
  • 8
    Great for all types of websites
  • 6
    Huge install and user base
  • 5
    Best
  • 5
    It's simple and easy to use by any novice
  • 5
    Perfect example of user collaboration
  • 5
    Open Source Community
  • 5
    Most websites make use of it
  • 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
  • 12
    Plugins are of mixed quality
  • 12
    Hard to keep up-to-date if you customize things
  • 9
    Not best backend UI
  • 2
    Complex Organization
  • 1
    Great Security

related WordPress posts

Dale Ross
Independent Contractor at Self Employed · | 22 upvotes · 1.2M 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
Siddhant Sharma
Tech Connoisseur at Channelize.io · | 12 upvotes · 913.9K views

WordPress Magento PHP Java Swift JavaScript

Back in the days, we started looking for a date on different matrimonial websites as there were no Dating Applications. We used to create different profiles. It all changed in 2012 when Tinder, an Online Dating application came into India Market.

Tinder allowed us to communicate with our potential soul mates. That too without paying any extra money. I too got 4-6 matches in 6 years. It changed the life of many Millennials. Tinder created a revolution of its own. P.S. - I still don't have a date :(

Posting my first article. Please have a look and do give feedback.

Communication InAppChat Dating Matrimonial #messaging

See more
Drupal logo

Drupal

10.1K
3.3K
346
Free, Open, Modular CMS written in PHP
10.1K
3.3K
+ 1
346
PROS OF DRUPAL
  • 73
    Stable, highly functional cms
  • 59
    Great community
  • 43
    Easy cms to make websites
  • 41
    Highly customizable
  • 21
    Digital customer experience delivery platform
  • 16
    Really powerful
  • 15
    Customizable
  • 10
    Flexible
  • 10
    Good tool for prototyping
  • 8
    Enterprise proven over many years when others failed
  • 7
    Open source
  • 7
    Each version becomes more intuitive for clients to use
  • 7
    Well documented
  • 7
    Headless adds even more power/flexibility
  • 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
Jan Vlnas
Developer Advocate at Superface · | 4 upvotes · 1.6K views

Depends on what options and technologies you have available, and how do you deploy your website.

There are CMSs which update existing static pages through FTP: You provide access credentials, mark editable parts of your HTML in a markup, and then edit the content through the hosted CMS. I know two systems which work like that: Cushy CMS and Surreal CMS.

If the source of your site is versioned through Git (and hosted on GitHub), you have other options, like Netlify CMS, Spinal CMS, Siteleaf, Forestry, or CloudCannon. Some of these also need you to use static site generator (like 11ty, Jekyll, or Hugo).

If you have some server-side scripting support available (typically PHP) you can also consider some flat-file based, server-side systems, like Kirby CMS or Lektor, which are usually simpler to retrofit into an existing template than “traditional” CMSs (WordPress, Drupal).

Finally, you could also use a desktop-based static site generator which provides a user-friendly GUI, and then locally generates and uploads the website. For example Publii, YouDoCMS, Agit CMS.

See more
ExpressJS logo

ExpressJS

24.4K
20.3K
1.6K
Sinatra inspired web development framework for node.js -- insanely fast, flexible, and simple
24.4K
20.3K
+ 1
1.6K
PROS OF EXPRESSJS
  • 377
    Simple
  • 333
    Node.js
  • 242
    Javascript
  • 192
    High performance
  • 150
    Robust routing
  • 71
    Middlewares
  • 70
    Open source
  • 57
    Great community
  • 36
    Hybrid web applications
  • 13
    Well documented
  • 9
    Sinatra inspired
  • 8
    Rapid development
  • 7
    Isomorphic js.. superfast and easy
  • 5
    Socket connection
  • 5
    Light weight
  • 4
    Npm
  • 4
    Resource available for learning
  • 3
    Event loop
  • 3
    Callbacks
  • 2
    Data stream
CONS OF EXPRESSJS
  • 27
    Not python
  • 17
    Overrated
  • 14
    No multithreading
  • 9
    Javascript
  • 5
    Not fast
  • 2
    Easily Insecure for Novices

related ExpressJS posts

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