Alternatives to Redwood logo

Alternatives to Redwood

Node.js, Django, ASP.NET, Laravel, and Android SDK are the most popular alternatives and competitors to Redwood.
13
23
+ 1
4

What is Redwood and what are its top alternatives?

It is an opinionated, full-stack, serverless web application framework that will allow you to build and deploy JAMstack applications with ease. Imagine a React frontend, statically delivered by CDN, that talks via GraphQL to your backend running on AWS Lambdas around the world, all deployable with just a git push—that's Redwood.
Redwood is a tool in the Frameworks (Full Stack) category of a tech stack.
Redwood is an open source tool with 8K GitHub stars and 354 GitHub forks. Here’s a link to Redwood's open source repository on GitHub

Top Alternatives to Redwood

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

  • Django

    Django

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

  • ASP.NET

    ASP.NET

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

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

  • Android SDK

    Android SDK

    Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment. ...

  • Spring Boot

    Spring Boot

    Spring Boot makes it easy to create stand-alone, production-grade Spring based Applications that you can "just run". We take an opinionated view of the Spring platform and third-party libraries so you can get started with minimum fuss. Most Spring Boot applications need very little Spring configuration. ...

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

  • .NET

    .NET

    .NET is a general purpose development platform. With .NET, you can use multiple languages, editors, and libraries to build native applications for web, mobile, desktop, gaming, and IoT for Windows, macOS, Linux, Android, and more. ...

Redwood alternatives & related posts

Node.js logo

Node.js

107.5K
88.4K
8.3K
A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
107.5K
88.4K
+ 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
    Allows us to reuse code in the frontend
  • 53
    Great modularity
  • 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.5M 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
Django logo

Django

23.8K
20.6K
3.6K
The Web framework for perfectionists with deadlines
23.8K
20.6K
+ 1
3.6K
PROS OF DJANGO
  • 617
    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
    Allows for very rapid development with great libraries
  • 7
    The Django community
  • 7
    ORM
  • 5
    Great MVC and templating engine
  • 5
    Its elegant and practical
  • 4
    Full stack
  • 4
    Mvt
  • 4
    Easy Structure , useful inbuilt library
  • 4
    Fast prototyping
  • 4
    Easy to develop end to end AI Models
  • 3
    Batteries included
  • 3
    Easy to use
  • 3
    King of backend world
  • 3
    Easy
  • 3
    Cross-Platform
  • 3
    Have not found anything that it can't do
  • 2
    Great peformance
  • 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
    Just the right level of abstraction
  • 2
    Scaffold
  • 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
    Python
  • 2
    Overwhelming folder structure
  • 2
    Bloated admin panel included
  • 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
ASP.NET logo

ASP.NET

19.8K
5.5K
7
An open source web framework for building modern web apps and services with .NET
19.8K
5.5K
+ 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
    Indie, Solo, Developer · | 8 upvotes · 760K 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

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

    Laravel

    18.4K
    14.4K
    3.4K
    A PHP Framework For Web Artisans
    18.4K
    14.4K
    + 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
    Android SDK logo

    Android SDK

    18.1K
    13.4K
    785
    An SDK that provides you the API libraries and developer tools necessary to build, test, and debug apps...
    18.1K
    13.4K
    + 1
    785
    PROS OF ANDROID SDK
    • 284
      Android development
    • 153
      Necessary for android
    • 127
      Android studio
    • 85
      Mobile framework
    • 81
      Backed by google
    • 26
      Platform-tools
    • 21
      Eclipse + adt plugin
    • 4
      Powerful, simple, one stop environment
    • 2
      Free
    • 2
      Больно
    CONS OF ANDROID SDK
      Be the first to leave a con

      related Android SDK posts

      Jesus Dario Rivera Rubio
      Telecomm Engineering at Netbeast · | 10 upvotes · 833K views

      We are using React Native in #SmartHome to share the business logic between Android and iOS team and approach users with a unique brand experience. The drawback is that we require lots of native Android SDK and Objective-C modules, so a good part of the invested time is there. The gain for a app that relies less on native communication, sensors and OS tools should be even higher.

      Also it helps us set different testing stages: we use Travis CI for the javascript (business logic), Bitrise to run build tests and @Detox for #end2end automated user tests.

      We use a microservices structure on top of Zeit's @now that read from firebase. We use JWT auth to authenticate requests among services and from users, following GitHub philosophy of using the same infrastructure than its API consumers. Firebase is used mainly as a key-value store between services and as a backup database for users. We also use its authentication mechanisms.

      You can be super locked-in if you also rely on it's analytics, but we use Amplitude for that, which offers us great insights. Intercom for communications with end-user and Mailjet for marketing.

      See more
      Sezgi Ulucam
      Developer Advocate at Hasura · | 7 upvotes · 621.8K views

      I've recently switched to using Expo for initializing and developing my React Native apps. Compared to React Native CLI, it's so much easier to get set up and going. Setting up and maintaining Android Studio, Android SDK, and virtual devices used to be such a headache. Thanks to Expo, I can now test my apps directly on my Android phone, just by installing the Expo app. I still use Xcode Simulator for iOS testing, since I don't have an iPhone, but that's easy anyway. The big win for me with Expo is ease of Android testing.

      The Expo SDK also provides convenient features like Facebook login, MapView, push notifications, and many others. https://docs.expo.io/versions/v31.0.0/sdk/

      See more
      Spring Boot logo

      Spring Boot

      15.1K
      13.1K
      873
      Create Spring-powered, production-grade applications and services with absolute minimum fuss
      15.1K
      13.1K
      + 1
      873
      PROS OF SPRING BOOT
      • 131
        Powerful and handy
      • 122
        Easy setup
      • 115
        Java
      • 84
        Spring
      • 80
        Fast
      • 40
        Extensible
      • 33
        Lots of "off the shelf" functionalities
      • 28
        Cloud Solid
      • 22
        Caches well
      • 20
        Many receipes around for obscure features
      • 19
        Modular
      • 19
        Productive
      • 18
        Integrations with most other Java frameworks
      • 17
        Spring ecosystem is great
      • 17
        Fast Performance With Microservices
      • 15
        Community
      • 14
        Auto-configuration
      • 12
        Easy setup, Community Support, Solid for ERP apps
      • 12
        One-stop shop
      • 11
        Cross-platform
      • 11
        Easy to parallelize
      • 10
        Easy setup, good for build erp systems, well documented
      • 10
        Powerful 3rd party libraries and frameworks
      • 9
        Easy setup, Git Integration
      • 2
        Kotlin
      • 2
        It's so easier to start a project on spring
      CONS OF SPRING BOOT
      • 18
        Heavy weight
      • 17
        Annotation ceremony
      • 10
        Many config files needed
      • 8
        Java
      • 5
        Reactive
      • 4
        Excellent tools for cloud hosting, since 5.x

      related Spring Boot posts

      Is learning Spring and Spring Boot for web apps back-end development is still relevant in 2021? Feel free to share your views with comparison to Django/Node.js/ ExpressJS or other frameworks.

      Please share some good beginner resources to start learning about spring/spring boot framework to build the web apps.

      See more
      Praveen Mooli
      Engineering Manager at Taylor and Francis · | 14 upvotes · 1.8M views

      We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

      To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

      To build #Webapps we decided to use Angular 2 with RxJS

      #Devops - GitHub , Travis CI , Terraform , Docker , Serverless

      See more
      Rails logo

      Rails

      14.4K
      9.8K
      5.4K
      Web development that doesn't hurt
      14.4K
      9.8K
      + 1
      5.4K
      PROS OF RAILS
      • 847
        Rapid development
      • 648
        Great gems
      • 604
        Great community
      • 479
        Convention over configuration
      • 416
        Mvc
      • 349
        Great for web
      • 344
        Beautiful code
      • 311
        Open source
      • 270
        Great libraries
      • 260
        Active record
      • 105
        Elegant
      • 87
        Easy to learn
      • 85
        Easy Database Migrations
      • 77
        Makes you happy
      • 72
        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
        API Development
      • 7
        Developer Friendly
      • 6
        Great documentation
      • 5
        Easy REST API creation
      • 5
        Quick
      • 4
        Haml and sass
      • 4
        Intuitive
      • 4
        Easy to learn, use, improvise and update
      • 4
        Great language
      • 2
        Legacy
      • 2
        Jet packs come standard
      • 2
        Easy and fast
      • 2
        Metaprogramming
      • 2
        It works
      • 1
        It's intuitive
      • 1
        Cancan
      • 1
        Easy Testing
      • 1
        Convention over configuration
      CONS OF RAILS
      • 20
        Too much "magic" (hidden behavior)
      • 13
        Poor raw performance
      • 11
        Asset system is too primitive and outdated
      • 6
        Bloat in models
      • 6
        Heavy use of mixins
      • 3
        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 · | 29 upvotes · 1.4M 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
      .NET logo

      .NET

      5.2K
      3.9K
      1.7K
      A free, cross-platform, open source developer platform for building many different types of applications
      5.2K
      3.9K
      + 1
      1.7K
      PROS OF .NET
      • 261
        Tight integration with visual studio
      • 250
        Stable code
      • 180
        Great community
      • 171
        Reliable and strongly typed server side language.
      • 132
        Microsoft
      • 108
        Fantastic documentation
      • 82
        Great 3rd party libraries
      • 71
        Speedy
      • 65
        Great azure integration
      • 57
        Great support
      • 25
        Highly productive
      • 24
        Linq
      • 23
        High Performance
      • 22
        Great programming languages (C#, VB)
      • 21
        C#
      • 19
        Open source
      • 13
        Clean markup with razor
      • 13
        Powerful Web application framework (ASP.NET MVC)
      • 13
        Powerful ORM (EntityFramework)
      • 11
        Fast
      • 9
        Constantly improving to keep up with new trends
      • 9
        Visual studio + Resharper = <3
      • 8
        Dependency injection
      • 7
        TFS
      • 6
        Job opportunities
      • 6
        High-Performance
      • 6
        Integrated and Reliable
      • 6
        Security
      • 5
        Huge ecosystem and communities
      • 5
        Light-weight
      • 4
        Variations
      • 4
        Lovely
      • 3
        Scaffolding
      • 3
        Support and SImplicity
      • 3
        {get; set;}
      • 3
        Asynchrony
      • 3
        Concurrent
      • 3
        Useful IoC
      • 2
        Entity framework
      • 2
        Default Debuging tools
      • 1
        Blazor
      CONS OF .NET
      • 9
        C#
      • 9
        Too expensive to deploy and maintain
      • 7
        Microsoft itself
      • 6
        Microsoft dependable systems
      • 3
        Hard learning curve
      • 1
        Not have a full fledged visual studio for linux

      related .NET posts

      Yshay Yaacobi

      Our first experience with .NET core was when we developed our OSS feature management platform - Tweek (https://github.com/soluto/tweek). We wanted to create a solution that is able to run anywhere (super important for OSS), has excellent performance characteristics and can fit in a multi-container architecture. We decided to implement our rule engine processor in F# , our main service was implemented in C# and other components were built using JavaScript / TypeScript and Go.

      Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.

      After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...

      See more
      John-Daniel Trask
      Co-founder & CEO at Raygun · | 23 upvotes · 203.2K views
      Shared insights
      on
      .NET
      Node.js
      at

      The core Web application of Raygun is still a Microsoft ASP.NET MVC application. Not too much has changed from a fundamental technology standpoint. We originally built using Mono, which just bled memory and would need to be constantly recycled. So we looked around at the options and what would be well suited to the highly transactional nature of our API. We settled on Node.js, feeling that the event loop model worked well given the lightweight workload of each message being processed. This served us well for several years.

      When we started to look at .NET Core in early 2016, it became quite obvious that being able to asynchronously hand off to our queuing service greatly improved throughput. Unfortunately, at the time, Node.js didn’t provide an easy mechanism to do this, while .NET Core had great concurrency capabilities from day one. This meant that our servers spent less time blocking on the hand off, and could start processing the next inbound message. This was the core component of the performance improvement.

      We chose .NET because it was a platform that our team was familiar with. Also we were skilled enough with it to know many performance tips and tricks to get the most from it. Due to this experience, it helped us get to market faster and deliver great performance.

      #Languages #FrameworksFullStack

      See more