Alternatives to Rails logo

Alternatives to Rails

Django, Ruby, Sinatra, React, and Laravel are the most popular alternatives and competitors to Rails.
16.5K
11.5K
+ 1
5.4K

What is Rails and what are its top alternatives?

Rails is a web-application framework that includes everything needed to create database-backed web applications according to the Model-View-Controller (MVC) pattern.
Rails is a tool in the Frameworks (Full Stack) category of a tech stack.
Rails is an open source tool with 50.8K GitHub stars and 20.4K GitHub forks. Here’s a link to Rails's open source repository on GitHub

Top Alternatives to Rails

  • Django
    Django

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

  • Ruby
    Ruby

    Ruby is a language of careful balance. Its creator, Yukihiro “Matz” Matsumoto, blended parts of his favorite languages (Perl, Smalltalk, Eiffel, Ada, and Lisp) to form a new language that balanced functional programming with imperative programming. ...

  • Sinatra
    Sinatra

    Sinatra is a DSL for quickly creating web applications in Ruby with minimal effort. ...

  • React
    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

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

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

  • Rake
    Rake

    It is a software task management and build automation tool. It allows the user to specify tasks and describe dependencies as well as to group tasks in a namespace. ...

  • ASP.NET
    ASP.NET

    .NET is a developer platform made up of tools, programming languages, and libraries for building many different types of applications. ...

Rails alternatives & related posts

Django logo

Django

29.8K
26.7K
3.9K
The Web framework for perfectionists with deadlines
29.8K
26.7K
+ 1
3.9K
PROS OF DJANGO
  • 641
    Rapid development
  • 474
    Open source
  • 407
    Great community
  • 357
    Easy to learn
  • 267
    Mvc
  • 218
    Beautiful code
  • 212
    Elegant
  • 196
    Free
  • 194
    Great packages
  • 182
    Great libraries
  • 71
    Restful
  • 67
    Comes with auth and crud admin panel
  • 67
    Powerful
  • 64
    Great documentation
  • 61
    Great for web
  • 48
    Python
  • 38
    Great orm
  • 36
    Great for api
  • 27
    All included
  • 22
    Web Apps
  • 22
    Fast
  • 19
    Used by top startups
  • 17
    Clean
  • 16
    Sexy
  • 16
    Easy setup
  • 13
    Convention over configuration
  • 12
    ORM
  • 9
    The Django community
  • 9
    Allows for very rapid development with great libraries
  • 7
    King of backend world
  • 7
    Great MVC and templating engine
  • 7
    Its elegant and practical
  • 6
    Mvt
  • 6
    Full stack
  • 6
    Fast prototyping
  • 6
    Have not found anything that it can't do
  • 6
    Cross-Platform
  • 5
    Batteries included
  • 5
    Very quick to get something up and running
  • 5
    Easy Structure , useful inbuilt library
  • 5
    Easy to develop end to end AI Models
  • 4
    Python community
  • 4
    Great peformance
  • 4
    Easy
  • 4
    Easy to use
  • 4
    Modular
  • 4
    Many libraries
  • 3
    Full-Text Search
  • 3
    Map
  • 3
    Zero code burden to change databases
  • 3
    Scaffold
  • 3
    Just the right level of abstraction
  • 2
    Easy to change database manager
  • 1
    Node js
  • 0
    Asdasd
  • 0
    Rails
  • 0
    Aaaa
  • 0
    Fastapi
CONS OF DJANGO
  • 25
    Underpowered templating
  • 21
    Autoreload restarts whole server
  • 20
    Underpowered ORM
  • 15
    URL dispatcher ignores HTTP method
  • 10
    Internal subcomponents coupling
  • 7
    Not nodejs
  • 7
    Configuration hell
  • 7
    Admin
  • 5
    Not as clean and nice documentation like Laravel
  • 3
    Bloated admin panel included
  • 3
    Not typed
  • 3
    Python
  • 2
    Overwhelming folder structure
  • 2
    InEffective Multithreading

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
Ruby logo

Ruby

27.9K
17.9K
3.9K
A dynamic, interpreted, open source programming language with a focus on simplicity and productivity
27.9K
17.9K
+ 1
3.9K
PROS OF RUBY
  • 601
    Programme friendly
  • 535
    Quick to develop
  • 487
    Great community
  • 467
    Productivity
  • 429
    Simplicity
  • 271
    Open source
  • 233
    Meta-programming
  • 203
    Powerful
  • 155
    Blocks
  • 138
    Powerful one-liners
  • 67
    Flexible
  • 57
    Easy to learn
  • 49
    Easy to start
  • 41
    Maintainability
  • 36
    Lambdas
  • 30
    Procs
  • 20
    Fun to write
  • 19
    Diverse web frameworks
  • 12
    Reads like English
  • 9
    Rails
  • 9
    Makes me smarter and happier
  • 8
    Elegant syntax
  • 7
    Very Dynamic
  • 6
    Matz
  • 5
    Programmer happiness
  • 4
    Generally fun but makes you wanna cry sometimes
  • 4
    Fun and useful
  • 4
    Object Oriented
  • 3
    Elegant code
  • 3
    Friendly
  • 3
    There are so many ways to make it do what you want
  • 3
    Easy packaging and modules
  • 2
    Primitive types can be tampered with
CONS OF RUBY
  • 7
    Memory hog
  • 7
    Really slow if you're not really careful
  • 3
    Nested Blocks can make code unreadable
  • 2
    Encouraging imperative programming
  • 1
    Ambiguous Syntax, such as function parentheses

related Ruby posts

Kamil Kowalski
Lead Architect at Fresha · | 28 upvotes · 1.4M views

When you think about test automation, it’s crucial to make it everyone’s responsibility (not just QA Engineers'). We started with Selenium and Java, but with our platform revolving around Ruby, Elixir and JavaScript, QA Engineers were left alone to automate tests. Cypress was the answer, as we could switch to JS and simply involve more people from day one. There's a downside too, as it meant testing on Chrome only, but that was "good enough" for us + if really needed we can always cover some specific cases in a different way.

See more
Jonathan Pugh
Software Engineer / Project Manager / Technical Architect · | 25 upvotes · 1.7M views

I needed to choose a full stack of tools for cross platform mobile application design & development. After much research and trying different tools, these are what I came up with that work for me today:

For the client coding I chose Framework7 because of its performance, easy learning curve, and very well designed, beautiful UI widgets. I think it's perfect for solo development or small teams. I didn't like React Native. It felt heavy to me and rigid. Framework7 allows the use of #CSS3, which I think is the best technology to come out of the #WWW movement. No other tech has been able to allow designers and developers to develop such flexible, high performance, customisable user interface elements that are highly responsive and hardware accelerated before. Now #CSS3 includes variables and flexboxes it is truly a powerful language and there is no longer a need for preprocessors such as #SCSS / #Sass / #less. React Native contains a very limited interpretation of #CSS3 which I found very frustrating after using #CSS3 for some years already and knowing its powerful features. The other very nice feature of Framework7 is that you can even build for the browser if you want your app to be available for desktop web browsers. The latest release also includes the ability to build for #Electron so you can have MacOS, Windows and Linux desktop apps. This is not possible with React Native yet.

Framework7 runs on top of Apache Cordova. Cordova and webviews have been slated as being slow in the past. Having a game developer background I found the tweeks to make it run as smooth as silk. One of those tweeks is to use WKWebView. Another important one was using srcset on images.

I use #Template7 for the for the templating system which is a no-nonsense mobile-centric #HandleBars style extensible templating system. It's easy to write custom helpers for, is fast and has a small footprint. I'm not forced into a new paradigm or learning some new syntax. It operates with standard JavaScript, HTML5 and CSS 3. It's written by the developer of Framework7 and so dovetails with it as expected.

I configured TypeScript to work with the latest version of Framework7. I consider TypeScript to be one of the best creations to come out of Microsoft in some time. They must have an amazing team working on it. It's very powerful and flexible. It helps you catch a lot of bugs and also provides code completion in supporting IDEs. So for my IDE I use Visual Studio Code which is a blazingly fast and silky smooth editor that integrates seamlessly with TypeScript for the ultimate type checking setup (both products are produced by Microsoft).

I use Webpack and Babel to compile the JavaScript. TypeScript can compile to JavaScript directly but Babel offers a few more options and polyfills so you can use the latest (and even prerelease) JavaScript features today and compile to be backwards compatible with virtually any browser. My favorite recent addition is "optional chaining" which greatly simplifies and increases readability of a number of sections of my code dealing with getting and setting data in nested objects.

I use some Ruby scripts to process images with ImageMagick and pngquant to optimise for size and even auto insert responsive image code into the HTML5. Ruby is the ultimate cross platform scripting language. Even as your scripts become large, Ruby allows you to refactor your code easily and make it Object Oriented if necessary. I find it the quickest and easiest way to maintain certain aspects of my build process.

For the user interface design and prototyping I use Figma. Figma has an almost identical user interface to #Sketch but has the added advantage of being cross platform (MacOS and Windows). Its real-time collaboration features are outstanding and I use them a often as I work mostly on remote projects. Clients can collaborate in real-time and see changes I make as I make them. The clickable prototyping features in Figma are also very well designed and mean I can send clickable prototypes to clients to try user interface updates as they are made and get immediate feedback. I'm currently also evaluating the latest version of #AdobeXD as an alternative to Figma as it has the very cool auto-animate feature. It doesn't have real-time collaboration yet, but I heard it is proposed for 2019.

For the UI icons I use Font Awesome Pro. They have the largest selection and best looking icons you can find on the internet with several variations in styles so you can find most of the icons you want for standard projects.

For the backend I was using the #GraphCool Framework. As I later found out, #GraphQL still has some way to go in order to provide the full power of a mature graph query language so later in my project I ripped out #GraphCool and replaced it with CouchDB and Pouchdb. Primarily so I could provide good offline app support. CouchDB with Pouchdb is very flexible and efficient combination and overcomes some of the restrictions I found in #GraphQL and hence #GraphCool also. The most impressive and important feature of CouchDB is its replication. You can configure it in various ways for backups, fault tolerance, caching or conditional merging of databases. CouchDB and Pouchdb even supports storing, retrieving and serving binary or image data or other mime types. This removes a level of complexity usually present in database implementations where binary or image data is usually referenced through an #HTML5 link. With CouchDB and Pouchdb apps can operate offline and sync later, very efficiently, when the network connection is good.

I use PhoneGap when testing the app. It auto-reloads your app when its code is changed and you can also install it on Android phones to preview your app instantly. iOS is a bit more tricky cause of Apple's policies so it's not available on the App Store, but you can build it and install it yourself to your device.

So that's my latest mobile stack. What tools do you use? Have you tried these ones?

See more
Sinatra logo

Sinatra

689
469
212
Classy web-development dressed in a DSL
689
469
+ 1
212
PROS OF SINATRA
  • 65
    Lightweight
  • 50
    Simple
  • 35
    Open source
  • 20
    Ruby
  • 13
    Great ecosystem of tools
  • 10
    Ease of use
  • 8
    If you know http you know sinatra
  • 5
    Large Community
  • 5
    Fast
  • 1
    Flexibilty and easy to use
CONS OF SINATRA
    Be the first to leave a con

    related Sinatra posts

    React logo

    React

    128.9K
    105.1K
    3.9K
    A JavaScript library for building user interfaces
    128.9K
    105.1K
    + 1
    3.9K
    PROS OF REACT
    • 775
      Components
    • 658
      Virtual dom
    • 567
      Performance
    • 492
      Simplicity
    • 438
      Composable
    • 176
      Data flow
    • 162
      Declarative
    • 124
      Isn't an mvc framework
    • 114
      Reactive updates
    • 111
      Explicit app state
    • 40
      JSX
    • 24
      Learn once, write everywhere
    • 19
      Uni-directional data flow
    • 17
      Easy to Use
    • 14
      Works great with Flux Architecture
    • 10
      Great perfomance
    • 8
      Built by Facebook
    • 7
      Javascript
    • 5
      Speed
    • 5
      TypeScript support
    • 4
      Easy to start
    • 4
      Scalable
    • 4
      Awesome
    • 4
      Feels like the 90s
    • 4
      Hooks
    • 3
      Excellent Documentation
    • 3
      Scales super well
    • 3
      Functional
    • 3
      Obama
    • 3
      Fancy third party tools
    • 3
      Server side views
    • 3
      Props
    • 3
      Server Side Rendering
    • 3
      Cross-platform
    • 2
      Rich ecosystem
    • 2
      Start simple
    • 2
      Allows creating single page applications
    • 2
      Sdfsdfsdf
    • 2
      Beautiful and Neat Component Management
    • 2
      Very gentle learning curve
    • 2
      Has functional components
    • 2
      Simple
    • 2
      Closer to standard JavaScript and HTML than others
    • 2
      Super easy
    • 2
      Has arrow functions
    • 2
      Strong Community
    • 2
      Great migration pathway for older systems
    • 2
      SSR
    • 2
      Fast evolving
    • 2
      Simple, easy to reason about and makes you productive
    • 2
      Just the View of MVC
    • 1
      Sharable
    • 1
      Every decision architecture wise makes sense
    • 1
      Permissively-licensed
    • 1
      Split your UI into components with one true state
    • 1
      Fragments
    • 0
      Recharts
    CONS OF REACT
    • 36
      Requires discipline to keep architecture organized
    • 23
      No predefined way to structure your app
    • 22
      Need to be familiar with lots of third party packages
    • 9
      JSX
    • 7
      Not enterprise friendly
    • 5
      One-way binding only
    • 2
      State consistency with backend neglected
    • 2
      Bad Documentation
    • 1
      Paradigms change too fast

    related React posts

    Vaibhav Taunk
    Team Lead at Technovert · | 31 upvotes · 1.9M views

    I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

    See more
    Adebayo Akinlaja
    Engineering Manager at Andela · | 27 upvotes · 1.1M views

    I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

    A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

    In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

    If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

    See more
    Laravel logo

    Laravel

    22.4K
    18.3K
    3.6K
    A PHP Framework For Web Artisans
    22.4K
    18.3K
    + 1
    3.6K
    PROS OF LARAVEL
    • 528
      Clean architecture
    • 379
      Growing community
    • 355
      Composer friendly
    • 328
      Open source
    • 307
      The only framework to consider for php
    • 208
      Mvc
    • 203
      Quickly develop
    • 161
      Dependency injection
    • 150
      Application architecture
    • 138
      Embraces good community packages
    • 67
      Write less, do more
    • 63
      Orm (eloquent)
    • 60
      Restful routing
    • 51
      Database migrations & seeds
    • 50
      Artisan scaffolding and migrations
    • 36
      Great documentation
    • 36
      Awesome
    • 27
      Awsome, Powerfull, Fast and Rapid
    • 25
      Build Apps faster, easier and better
    • 25
      Promotes elegant coding
    • 22
      Eloquent ORM
    • 22
      Modern PHP
    • 22
      JSON friendly
    • 22
      Easy to learn, scalability
    • 21
      Most easy for me
    • 20
      Beautiful
    • 20
      Test-Driven
    • 20
      Blade Template
    • 14
      Security
    • 13
      Based on SOLID
    • 12
      Clean Documentation
    • 12
      Cool
    • 11
      Simple
    • 11
      Convention over Configuration
    • 11
      Easy to attach Middleware
    • 10
      Easy Request Validatin
    • 9
      Fast
    • 9
      Simpler
    • 9
      Easy to use
    • 8
      Laravel + Cassandra = Killer Framework
    • 8
      Its just wow
    • 8
      Friendly API
    • 8
      Get going quickly straight out of the box. BYOKDM
    • 7
      Simplistic , easy and faster
    • 7
      Super easy and powerful
    • 7
      Less dependencies
    • 6
      Great customer support
    • 6
      Its beautiful to code in
    • 5
      The only "cons" is wrong! No static method just Facades
    • 5
      Fast and Clarify framework
    • 5
      Active Record
    • 5
      Php7
    • 5
      Speed
    • 5
      Easy
    • 4
      Composer
    • 4
      Laravel Mix
    • 4
      Minimum system requirements
    • 4
      Easy views handling and great ORM
    • 4
      Eloquent
    • 4
      Laragon
    • 3
      Laravel Spark
    • 3
      Ease of use
    • 3
      Cashier with Braintree and Stripe
    • 3
      Laravel Forge and Envoy
    • 3
      Laravel Horizon and Telescope
    • 3
      Laravel Nova
    • 3
      Laravel casher
    • 3
      Laravel Passport
    • 3
      Intuitive usage
    • 2
      Heart touch
    • 2
      Rapid development
    • 2
      Laravel love live long
    • 2
      Like heart beat
    • 2
      Touch heart artisan
    • 2
      Scout
    • 1
      Deployment
    CONS OF LARAVEL
    • 44
      PHP
    • 30
      Too many dependency
    • 21
      Slower than the other two
    • 17
      A lot of static method calls for convenience
    • 14
      Too many include
    • 11
      Heavy
    • 7
      Bloated
    • 6
      Laravel
    • 5
      Confusing
    • 5
      Too underrated
    • 4
      Does not work well for file uploads in Shared Hosting
    • 2
      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
    Node.js logo

    Node.js

    142.6K
    119.5K
    8.5K
    A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
    142.6K
    119.5K
    + 1
    8.5K
    PROS OF NODE.JS
    • 1.4K
      Npm
    • 1.3K
      Javascript
    • 1.1K
      Great libraries
    • 1K
      High-performance
    • 799
      Open source
    • 485
      Great for apis
    • 475
      Asynchronous
    • 420
      Great community
    • 390
      Great for realtime apps
    • 295
      Great for command line utilities
    • 81
      Websockets
    • 81
      Node Modules
    • 68
      Uber Simple
    • 59
      Great modularity
    • 57
      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
      Cross platform
    • 10
      Scalability
    • 9
      Simple
    • 8
      Mean Stack
    • 7
      Easy concurrency
    • 7
      Great for webapps
    • 6
      React
    • 6
      Fast, simple code and async
    • 6
      Friendly
    • 6
      Typescript
    • 5
      Great speed
    • 5
      Fast development
    • 5
      Its amazingly fast and scalable
    • 5
      Control everything
    • 5
      Scalable
    • 5
      Easy to use and fast and goes well with JSONdb's
    • 4
      It's fast
    • 4
      Easy to use
    • 4
      Isomorphic coolness
    • 3
      Easy to learn
    • 3
      Easy
    • 3
      Javascript2
    • 3
      Great community
    • 3
      Not Python
    • 3
      Sooper easy for the Backend connectivity
    • 3
      TypeScript Support
    • 3
      Scales, fast, simple, great community, npm, express
    • 3
      One language, end-to-end
    • 3
      Less boilerplate code
    • 3
      Performant and fast prototyping
    • 3
      Blazing fast
    • 2
      Npm i ape-updating
    • 2
      Event Driven
    • 2
      Lovely
    CONS OF NODE.JS
    • 46
      Bound to a single CPU
    • 42
      New framework every day
    • 37
      Lots of terrible examples on the internet
    • 29
      Asynchronous programming is the worst
    • 23
      Callback
    • 18
      Javascript
    • 11
      Dependency based on GitHub
    • 10
      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
    • 1
      Bad transitive dependency management
    • 1
      Can't read server session
    • 1
      No standard approach

    related Node.js posts

    Nick Rockwell
    SVP, Engineering at Fastly · | 44 upvotes · 1.9M 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 · | 40 upvotes · 4.9M 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
    Rake logo

    Rake

    57
    32
    0
    A software task management and build automation tool
    57
    32
    + 1
    0
    PROS OF RAKE
      Be the first to leave a pro
      CONS OF RAKE
        Be the first to leave a con

        related Rake posts

        ASP.NET logo

        ASP.NET

        23.1K
        8.1K
        18
        An open source web framework for building modern web apps and services with .NET
        23.1K
        8.1K
        + 1
        18
        PROS OF ASP.NET
        • 13
          Great mvc
        • 5
          Easy to learn
        CONS OF ASP.NET
        • 1
          Not highly flexible for advance Developers
        • 1
          Entity framework is very slow

        related ASP.NET posts

        Greg Neumann
        Indie, Solo, Developer · | 8 upvotes · 915K views

        Finding the most effective dev stack for a solo developer. Over the past year, I've been looking at many tech stacks that would be 'best' for me, as a solo, indie, developer to deliver a desktop app (Windows & Mac) plus mobile - iOS mainly. Initially, Xamarin started to stand-out. Using .NET Core as the run-time, Xamarin as the native API provider and Xamarin Forms for the UI seemed to solve all issues. But, the cracks soon started to appear. Xamarin Forms is mobile only; the Windows incarnation is different. There is no Mac UI solution (you have to code it natively in Mac OS Storyboard. I was also worried how Xamarin Forms , if I was to use it, was going to cope, in future, with Apple's new SwiftUI and Google's new Fuchsia.

        This plethora of techs for the UI-layer made me reach for the safer waters of using Web-techs for the UI. Lovely! Consistency everywhere (well, mostly). But that consistency evaporates when platform issues are addressed. There are so many web frameworks!

        But, I made a simple decision. It's just me...I am clever, but there is no army of coders here. And I have big plans for a business app. How could just 1 developer go-on to deploy a decent app to Windows, iPhone, iPad & Mac OS? I remembered earlier days when I've used Microsoft's ASP.NET to scaffold - generate - loads of Code for a web-app that I needed for several charities that I worked with. What 'generators' exist that do a lot of the platform-specific rubbish, allow the necessary customisation of such platform integration and provide a decent UI?

        I've placed my colours to the Quasar Framework mast. Oh dear, that means Electron desktop apps doesn't it? Well, Ive had enough of loads of Developers saying that "the menus won't look native" or "it uses too much RAM" and so on. I've been using non-native UI-wrapped apps for ages - the date picker in Outlook on iOS is way better than the native date-picker and I'd been using it for years without getting hot under the collar about it. Developers do get so hung-up on things that busy Users hardly notice; don't you think?. As to the RAM usage issue; that's a bit true. But Users only really notice when an app uses so much RAM that the machine starts to page-out. Electron contributes towards that horizon but does not cause it. My Users will be business-users after all. Somewhat decent machines.

        Looking forward to all that lovely Vue.js around my TypeScript and all those really, really, b e a u t I f u l UI controls of Quasar Framework . Still not sure that 1 dev can deliver all that... but I'm up for trying...

        See more

        Hi. We are planning to develop web, desktop, and mobile app for procurement, logistics, and contracts. Procure to Pay and Source to pay, spend management, supplier management, catalog management. ( similar to SAP Ariba, gap.com, coupa.com, ivalua.com vroozi.com, procurify.com

        We got stuck when deciding which technology stack is good for the future. We look forward to your kind guidance that will help us.

        We want to integrate with multiple databases with seamless bidirectional integration. What APIs and middleware available are best to achieve this? SAP HANA, Oracle, MySQL, MongoDB...

        ASP.NET / Node.js / Laravel. ......?

        Please guide us

        See more