Alternatives to Phoenix Framework logo

Alternatives to Phoenix Framework

Vapor, Django, WordPress, Laravel, and Rails are the most popular alternatives and competitors to Phoenix Framework.
836
924
+ 1
667

What is Phoenix Framework and what are its top alternatives?

Phoenix is a framework for building HTML5 apps, API backends and distributed systems. Written in Elixir, you get beautiful syntax, productive tooling and a fast runtime.
Phoenix Framework is a tool in the Frameworks (Full Stack) category of a tech stack.
Phoenix Framework is an open source tool with 18.9K GitHub stars and 2.6K GitHub forks. Here’s a link to Phoenix Framework's open source repository on GitHub

Top Alternatives to Phoenix Framework

  • Vapor
    Vapor

    Vapor is the first true web framework for Swift. It provides a beautifully expressive foundation for your app without tying you to any single server implementation. ...

  • Django
    Django

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

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

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

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

  • Golang
    Golang

    Go is expressive, concise, clean, and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines, while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast, statically typed, compiled language that feels like a dynamically typed, interpreted language. ...

  • Rocket
    Rocket

    Rocket is a web framework for Rust that makes it simple to write fast web applications without sacrificing flexibility or type safety. All with minimal code. ...

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

Phoenix Framework alternatives & related posts

Vapor logo

Vapor

102
190
58
A type-safe web framework for Swift
102
190
+ 1
58
PROS OF VAPOR
  • 12
    Fast
  • 10
    Swift
  • 9
    Type-safe
  • 5
    Great for apis
  • 5
    Readable
  • 5
    Good Abstraction
  • 5
    Asynchronous
  • 4
    Compiled to machine code
  • 3
    Maintainable
CONS OF VAPOR
  • 1
    Server side swift is still in its infancy
  • 1
    Not as much support available.

related Vapor posts

Django logo

Django

32.5K
29.5K
4K
The Web framework for perfectionists with deadlines
32.5K
29.5K
+ 1
4K
PROS OF DJANGO
  • 653
    Rapid development
  • 479
    Open source
  • 413
    Great community
  • 366
    Easy to learn
  • 270
    Mvc
  • 223
    Beautiful code
  • 215
    Elegant
  • 198
    Free
  • 196
    Great packages
  • 184
    Great libraries
  • 74
    Restful
  • 72
    Comes with auth and crud admin panel
  • 71
    Powerful
  • 69
    Great documentation
  • 64
    Great for web
  • 51
    Python
  • 39
    Great orm
  • 37
    Great for api
  • 28
    All included
  • 25
    Fast
  • 23
    Web Apps
  • 20
    Used by top startups
  • 20
    Clean
  • 19
    Easy setup
  • 17
    Sexy
  • 14
    Convention over configuration
  • 13
    Allows for very rapid development with great libraries
  • 13
    ORM
  • 12
    The Django community
  • 10
    King of backend world
  • 9
    Great MVC and templating engine
  • 7
    Full stack
  • 7
    Batteries included
  • 7
    Its elegant and practical
  • 6
    Fast prototyping
  • 6
    Very quick to get something up and running
  • 6
    Mvt
  • 6
    Cross-Platform
  • 6
    Have not found anything that it can't do
  • 5
    Easy Structure , useful inbuilt library
  • 5
    Easy to develop end to end AI Models
  • 5
    Zero code burden to change databases
  • 4
    Map
  • 4
    Easy to change database manager
  • 4
    Easy
  • 4
    Great peformance
  • 4
    Many libraries
  • 4
    Python community
  • 4
    Modular
  • 4
    Easy to use
  • 3
    Just the right level of abstraction
  • 3
    Scaffold
  • 3
    Full-Text Search
  • 1
    Scalable
  • 1
    Node js
  • 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
WordPress logo

WordPress

90.2K
33.8K
2.1K
A semantic personal publishing platform with a focus on aesthetics, web standards, and usability.
90.2K
33.8K
+ 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 · 916.4K 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
Laravel logo

Laravel

24.3K
20.1K
3.7K
A PHP Framework For Web Artisans
24.3K
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
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.7M 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
Golang logo

Golang

14.7K
13K
3.2K
An open source programming language that makes it easy to build simple, reliable, and efficient software
14.7K
13K
+ 1
3.2K
PROS OF GOLANG
  • 534
    High-performance
  • 389
    Simple, minimal syntax
  • 356
    Fun to write
  • 297
    Easy concurrency support via goroutines
  • 269
    Fast compilation times
  • 191
    Goroutines
  • 178
    Statically linked binaries that are simple to deploy
  • 149
    Simple compile build/run procedures
  • 135
    Backed by google
  • 132
    Great community
  • 51
    Garbage collection built-in
  • 43
    Built-in Testing
  • 42
    Excellent tools - gofmt, godoc etc
  • 38
    Elegant and concise like Python, fast like C
  • 35
    Awesome to Develop
  • 25
    Used for Docker
  • 24
    Flexible interface system
  • 22
    Deploy as executable
  • 22
    Great concurrency pattern
  • 19
    Open-source Integration
  • 16
    Fun to write and so many feature out of the box
  • 15
    Easy to read
  • 15
    Go is God
  • 14
    Its Simple and Heavy duty
  • 13
    Powerful and simple
  • 13
    Easy to deploy
  • 12
    Best language for concurrency
  • 11
    Concurrency
  • 10
    Safe GOTOs
  • 10
    Rich standard library
  • 9
    Clean code, high performance
  • 9
    Easy setup
  • 8
    High performance
  • 8
    Hassle free deployment
  • 8
    Simplicity, Concurrency, Performance
  • 7
    Used by Giants of the industry
  • 7
    Single binary avoids library dependency issues
  • 6
    Cross compiling
  • 6
    Simple, powerful, and great performance
  • 5
    Gofmt
  • 5
    Garbage Collection
  • 5
    Very sophisticated syntax
  • 5
    Excellent tooling
  • 5
    WYSIWYG
  • 4
    Keep it simple and stupid
  • 4
    Widely used
  • 4
    Kubernetes written on Go
  • 2
    No generics
  • 1
    Operator goto
CONS OF GOLANG
  • 41
    You waste time in plumbing code catching errors
  • 25
    Verbose
  • 23
    Packages and their path dependencies are braindead
  • 15
    Dependency management when working on multiple projects
  • 15
    Google's documentations aren't beginer friendly
  • 10
    Automatic garbage collection overheads
  • 8
    Uncommon syntax
  • 6
    Type system is lacking (no generics, etc)
  • 3
    Collection framework is lacking (list, set, map)
  • 2
    Best programming language

related Golang posts

Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 41 upvotes · 5.6M 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
Nick Parsons
Building cool things on the internet 🛠️ at Stream · | 35 upvotes · 1.8M views

Winds 2.0 is an open source Podcast/RSS reader developed by Stream with a core goal to enable a wide range of developers to contribute.

We chose JavaScript because nearly every developer knows or can, at the very least, read JavaScript. With ES6 and Node.js v10.x.x, it’s become a very capable language. Async/Await is powerful and easy to use (Async/Await vs Promises). Babel allows us to experiment with next-generation JavaScript (features that are not in the official JavaScript spec yet). Yarn allows us to consistently install packages quickly (and is filled with tons of new tricks)

We’re using JavaScript for everything – both front and backend. Most of our team is experienced with Go and Python, so Node was not an obvious choice for this app.

Sure... there will be haters who refuse to acknowledge that there is anything remotely positive about JavaScript (there are even rants on Hacker News about Node.js); however, without writing completely in JavaScript, we would not have seen the results we did.

#FrameworksFullStack #Languages

See more
Rocket logo

Rocket

74
148
11
Web Framework for Rust
74
148
+ 1
11
PROS OF ROCKET
  • 4
    Easy to use
  • 4
    Uses all the rust features extensively
  • 1
    Inbuilt templating feature
  • 1
    Django analog in rust
  • 1
    Provides nice abstractions
CONS OF ROCKET
  • 1
    Only runs in nightly

related Rocket posts

Node.js logo

Node.js

154.6K
134.3K
8.5K
A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
154.6K
134.3K
+ 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.6M 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