Alternatives to Rails logo

Alternatives to Rails

Django, Ruby, Sinatra, React, and Laravel are the most popular alternatives and competitors to Rails.
14.5K
9.9K
+ 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 48.5K GitHub stars and 19.5K 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

23.9K
20.7K
3.6K
The Web framework for perfectionists with deadlines
23.9K
20.7K
+ 1
3.6K
PROS OF DJANGO
  • 619
    Rapid development
  • 459
    Open source
  • 394
    Great community
  • 344
    Easy to learn
  • 256
    Mvc
  • 208
    Beautiful code
  • 207
    Elegant
  • 187
    Free
  • 186
    Great packages
  • 173
    Great libraries
  • 63
    Restful
  • 60
    Powerful
  • 59
    Comes with auth and crud admin panel
  • 55
    Great documentation
  • 52
    Great for web
  • 41
    Python
  • 35
    Great orm
  • 31
    Great for api
  • 24
    All included
  • 20
    Web Apps
  • 19
    Fast
  • 16
    Used by top startups
  • 14
    Clean
  • 13
    Sexy
  • 12
    Easy setup
  • 10
    Convention over configuration
  • 7
    ORM
  • 7
    Allows for very rapid development with great libraries
  • 7
    The Django community
  • 5
    Its elegant and practical
  • 5
    Great MVC and templating engine
  • 4
    Full stack
  • 4
    Mvt
  • 4
    Easy Structure , useful inbuilt library
  • 4
    Fast prototyping
  • 4
    Easy to develop end to end AI Models
  • 3
    Easy
  • 3
    Easy to use
  • 3
    King of backend world
  • 3
    Cross-Platform
  • 3
    Batteries included
  • 3
    Have not found anything that it can't do
  • 2
    Scaffold
  • 2
    Zero code burden to change databases
  • 2
    Full-Text Search
  • 2
    Map
  • 2
    Modular
  • 2
    Very quick to get something up and running
  • 2
    Many libraries
  • 2
    Python community
  • 2
    Great peformance
  • 2
    Just the right level of abstraction
  • 1
    Easy to change database manager
CONS OF DJANGO
  • 24
    Underpowered templating
  • 19
    Underpowered ORM
  • 18
    Autoreload restarts whole server
  • 15
    URL dispatcher ignores HTTP method
  • 10
    Internal subcomponents coupling
  • 7
    Not nodejs
  • 7
    Admin
  • 6
    Configuration hell
  • 3
    Not as clean and nice documentation like Laravel
  • 3
    Bloated admin panel included
  • 3
    Python
  • 2
    Overwhelming folder structure
  • 2
    Not typed
  • 1
    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

22.7K
14.9K
3.9K
A dynamic, interpreted, open source programming language with a focus on simplicity and productivity
22.7K
14.9K
+ 1
3.9K
PROS OF RUBY
  • 600
    Programme friendly
  • 533
    Quick to develop
  • 488
    Great community
  • 467
    Productivity
  • 430
    Simplicity
  • 272
    Open source
  • 234
    Meta-programming
  • 203
    Powerful
  • 157
    Blocks
  • 138
    Powerful one-liners
  • 65
    Flexible
  • 56
    Easy to learn
  • 48
    Easy to start
  • 40
    Maintainability
  • 36
    Lambdas
  • 30
    Procs
  • 19
    Diverse web frameworks
  • 19
    Fun to write
  • 11
    Reads like English
  • 8
    Rails
  • 8
    Makes me smarter and happier
  • 7
    Elegant syntax
  • 6
    Very Dynamic
  • 5
    Programmer happiness
  • 5
    Matz
  • 4
    Generally fun but makes you wanna cry sometimes
  • 4
    Fun and useful
  • 3
    Friendly
  • 3
    Object Oriented
  • 3
    There are so many ways to make it do what you want
  • 2
    Easy packaging and modules
  • 2
    Primitive types can be tampered with
  • 2
    Elegant code
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 · | 27 upvotes · 944.7K 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.4M 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

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

    related Sinatra posts

    React logo

    React

    97.9K
    77.8K
    3.8K
    A JavaScript library for building user interfaces
    97.9K
    77.8K
    + 1
    3.8K
    PROS OF REACT
    • 751
      Components
    • 651
      Virtual dom
    • 558
      Performance
    • 484
      Simplicity
    • 436
      Composable
    • 174
      Data flow
    • 159
      Declarative
    • 123
      Isn't an mvc framework
    • 113
      Reactive updates
    • 110
      Explicit app state
    • 31
      JSX
    • 23
      Learn once, write everywhere
    • 18
      Uni-directional data flow
    • 16
      Easy to Use
    • 14
      Works great with Flux Architecture
    • 10
      Great perfomance
    • 8
      Built by Facebook
    • 6
      Javascript
    • 5
      Speed
    • 5
      TypeScript support
    • 4
      Awesome
    • 4
      Easy to start
    • 4
      Feels like the 90s
    • 4
      Scalable
    • 3
      Hooks
    • 3
      Fancy third party tools
    • 3
      Server side views
    • 3
      Functional
    • 2
      Simple
    • 2
      Great migration pathway for older systems
    • 2
      Server Side Rendering
    • 2
      Cross-platform
    • 2
      SSR
    • 2
      Fast evolving
    • 2
      Simple, easy to reason about and makes you productive
    • 2
      Rich ecosystem
    • 2
      Has functional components
    • 2
      Has arrow functions
    • 2
      Strong Community
    • 2
      Closer to standard JavaScript and HTML than others
    • 2
      Very gentle learning curve
    • 2
      Excellent Documentation
    • 2
      Super easy
    • 2
      Props
    • 2
      Scales super well
    • 2
      Just the View of MVC
    • 1
      Www
    • 1
      Start simple
    • 1
      Sdfsdfsdf
    • 1
      Obama
    • 1
      Fragments
    • 1
      Split your UI into components with one true state
    • 1
      Sharable
    • 1
      Every decision architecture wise makes sense
    • 1
      Permissively-licensed
    • 1
      Beautiful and Neat Component Management
    • 1
      Allows creating single page applications
    CONS OF REACT
    • 33
      Requires discipline to keep architecture organized
    • 21
      No predefined way to structure your app
    • 20
      Need to be familiar with lots of third party packages
    • 6
      JSX
    • 6
      Not enterprise friendly
    • 1
      One-way binding only
    • 1
      State consistency with backend neglected

    related React posts

    Vaibhav Taunk
    Team Lead at Technovert · | 31 upvotes · 1.5M 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
    Johnny Bell
    Software Engineer at Weedmaps · | 26 upvotes · 387.5K views
    Shared insights
    on
    Vue.js
    React

    I've used both Vue.js and React and I would stick with React. I know that Vue.js seems easier to write and its much faster to pick up however as you mentioned above React has way more ready made components you can just plugin, and the community for React is very big.

    It might be a bit more of a steep learning curve for your friend to learn React over Vue.js but I think in the long run its the better option.

    See more
    Laravel logo

    Laravel

    18.5K
    14.5K
    3.4K
    A PHP Framework For Web Artisans
    18.5K
    14.5K
    + 1
    3.4K
    PROS OF LARAVEL
    • 504
      Clean architecture
    • 364
      Growing community
    • 339
      Composer friendly
    • 315
      Open source
    • 295
      The only framework to consider for php
    • 194
      Mvc
    • 189
      Quickly develop
    • 155
      Dependency injection
    • 143
      Application architecture
    • 129
      Embraces good community packages
    • 57
      Write less, do more
    • 52
      Restful routing
    • 47
      Orm (eloquent)
    • 43
      Artisan scaffolding and migrations
    • 42
      Database migrations & seeds
    • 35
      Awesome
    • 33
      Great documentation
    • 25
      Awsome, Powerfull, Fast and Rapid
    • 25
      Promotes elegant coding
    • 24
      Build Apps faster, easier and better
    • 22
      Easy to learn, scalability
    • 22
      JSON friendly
    • 21
      Most easy for me
    • 21
      Eloquent ORM
    • 19
      Modern PHP
    • 19
      Test-Driven
    • 18
      Beautiful
    • 18
      Blade Template
    • 13
      Security
    • 11
      Based on SOLID
    • 11
      Clean Documentation
    • 10
      Cool
    • 10
      Easy to attach Middleware
    • 10
      Simple
    • 10
      Convention over Configuration
    • 9
      Easy Request Validatin
    • 8
      Simpler
    • 8
      Get going quickly straight out of the box. BYOKDM
    • 8
      Its just wow
    • 8
      Fast
    • 8
      Laravel + Cassandra = Killer Framework
    • 8
      Easy to use
    • 7
      Super easy and powerful
    • 7
      Friendly API
    • 7
      Less dependencies
    • 7
      Simplistic , easy and faster
    • 6
      Great customer support
    • 6
      Its beautiful to code in
    • 5
      Php7
    • 5
      Active Record
    • 5
      Fast and Clarify framework
    • 5
      Easy
    • 5
      The only "cons" is wrong! No static method just Facades
    • 5
      Speed
    • 4
      Eloquent
    • 4
      Easy views handling and great ORM
    • 4
      Minimum system requirements
    • 4
      Laravel Mix
    • 4
      Composer
    • 4
      Laragon
    • 3
      Laravel Nova
    • 3
      Laravel casher
    • 3
      Laravel Spark
    • 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
    • 2
      Heart touch
    • 2
      Like heart beat
    • 2
      Touch heart artisan
    • 2
      Scout
    • 2
      Rapid development
    • 2
      Laravel love live long
    CONS OF LARAVEL
    • 40
      PHP
    • 27
      Too many dependency
    • 19
      Slower than the other two
    • 15
      A lot of static method calls for convenience
    • 13
      Too many include
    • 10
      Heavy
    • 7
      Bloated
    • 6
      Laravel
    • 5
      Confusing
    • 4
      Does not work well for file uploads in Shared Hosting
    • 3
      Too underrated
    • 2
      Not fast with MongoDB
    • 1
      Difficult to learn
    • 1
      Not using SOLID principles

    related Laravel posts

    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
    CDG

    I use Laravel because it's the most advances PHP framework out there, easy to maintain, easy to upgrade and most of all : easy to get a handle on, and to follow every new technology ! PhpStorm is our main software to code, as of simplicity and full range of tools for a modern application.

    Google Analytics Analytics of course for a tailored analytics, Bulma as an innovative CSS framework, coupled with our Sass (Scss) pre-processor.

    As of more basic stuff, we use HTML5, JavaScript (but with Vue.js too) and Webpack to handle the generation of all this.

    To deploy, we set up Buddy to easily send the updates on our nginx / Ubuntu server, where it will connect to our GitHub Git private repository, pull and do all the operations needed with Deployer .

    CloudFlare ensure the rapidity of distribution of our content, and Let's Encrypt the https certificate that is more than necessary when we'll want to sell some products with our Stripe api calls.

    Asana is here to let us list all the functionalities, possibilities and ideas we want to implement.

    See more
    Node.js logo

    Node.js

    108.1K
    88.9K
    8.3K
    A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
    108.1K
    88.9K
    + 1
    8.3K
    PROS OF NODE.JS
    • 1.4K
      Npm
    • 1.3K
      Javascript
    • 1.1K
      Great libraries
    • 1K
      High-performance
    • 791
      Open source
    • 480
      Great for apis
    • 471
      Asynchronous
    • 417
      Great community
    • 387
      Great for realtime apps
    • 292
      Great for command line utilities
    • 78
      Node Modules
    • 76
      Websockets
    • 65
      Uber Simple
    • 53
      Great modularity
    • 53
      Allows us to reuse code in the frontend
    • 38
      Easy to start
    • 33
      Great for Data Streaming
    • 29
      Realtime
    • 25
      Awesome
    • 23
      Non blocking IO
    • 16
      Can be used as a proxy
    • 15
      High performance, open source, scalable
    • 14
      Non-blocking and modular
    • 13
      Easy and Fun
    • 12
      Same lang as AngularJS
    • 11
      Easy and powerful
    • 10
      Future of BackEnd
    • 9
      Fast
    • 8
      Scalability
    • 8
      Cross platform
    • 8
      Fullstack
    • 7
      Mean Stack
    • 7
      Simple
    • 5
      Easy concurrency
    • 5
      Great for webapps
    • 5
      React
    • 4
      Friendly
    • 4
      Easy to use and fast and goes well with JSONdb's
    • 4
      Typescript
    • 4
      Fast, simple code and async
    • 3
      Its amazingly fast and scalable
    • 3
      Scalable
    • 3
      Great speed
    • 3
      Fast development
    • 3
      Isomorphic coolness
    • 3
      Control everything
    • 2
      It's fast
    • 2
      Not Python
    • 2
      Blazing fast
    • 2
      One language, end-to-end
    • 2
      TypeScript Support
    • 2
      Easy to learn
    • 2
      Javascript2
    • 2
      Easy to use
    • 2
      Less boilerplate code
    • 2
      Sooper easy for the Backend connectivity
    • 2
      Great community
    • 2
      Scales, fast, simple, great community, npm, express
    • 2
      Performant and fast prototyping
    • 1
      Easy
    • 1
      Lovely
    • 0
      Event Driven
    CONS OF NODE.JS
    • 46
      Bound to a single CPU
    • 40
      New framework every day
    • 34
      Lots of terrible examples on the internet
    • 28
      Asynchronous programming is the worst
    • 22
      Callback
    • 16
      Javascript
    • 11
      Dependency based on GitHub
    • 10
      Dependency hell
    • 10
      Low computational power
    • 7
      Can block whole server easily
    • 6
      Very very Slow
    • 6
      Callback functions may not fire on expected sequence
    • 3
      Unneeded over complication
    • 3
      Unstable
    • 3
      Breaking updates
    • 1
      No standard approach

    related Node.js posts

    Nick Rockwell
    SVP, Engineering at Fastly · | 42 upvotes · 1.6M 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 · | 38 upvotes · 3.7M 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

    54
    29
    0
    A software task management and build automation tool
    54
    29
    + 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

        19.9K
        5.6K
        7
        An open source web framework for building modern web apps and services with .NET
        19.9K
        5.6K
        + 1
        7
        PROS OF ASP.NET
        • 7
          Great mvc
        CONS OF ASP.NET
          Be the first to leave a con

          related ASP.NET posts

          Greg Neumann

          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

          I found Heroku to be a great option to get ExpressJS up and running with very little hustle. The free tier is great, but I'd recommend to set up a cronjob to visit your site every few minutes so that the server stays awake. Netlify was the option to host the front-end because doing the server side rendering on #Heroku would have taken a little more time than I'd like to. For the moment pre-rendering the app with prerender-spa-plugin is enough to help with #seo. Puppeteer was my choice over other options because it made it easier to scrape websites made on ASP.NET which is what I needed in this case. And Vue.js is my top choice at the moment because it's really beginner friendly and it has a lot of the features I like about Angular 2 and React. vuex is a must in most of the app I build.

          See more