Alternatives to .NET logo

Alternatives to .NET

ASP.NET, Java, Python, PHP, and JavaScript are the most popular alternatives and competitors to .NET.
5.9K
4.8K
+ 1
1.8K

What is .NET and what are its top alternatives?

.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.
.NET is a tool in the Frameworks (Full Stack) category of a tech stack.
.NET is an open source tool with 17.9K GitHub stars and 4.6K GitHub forks. Here’s a link to .NET's open source repository on GitHub

Top Alternatives to .NET

  • ASP.NET
    ASP.NET

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

  • Java
    Java

    Java is a programming language and computing platform first released by Sun Microsystems in 1995. There are lots of applications and websites that will not work unless you have Java installed, and more are created every day. Java is fast, secure, and reliable. From laptops to datacenters, game consoles to scientific supercomputers, cell phones to the Internet, Java is everywhere! ...

  • Python
    Python

    Python is a general purpose programming language created by Guido Van Rossum. Python is most praised for its elegant syntax and readable code, if you are just beginning your programming career python suits you best. ...

  • PHP
    PHP

    Fast, flexible and pragmatic, PHP powers everything from your blog to the most popular websites in the world. ...

  • JavaScript
    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

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

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

.NET alternatives & related posts

ASP.NET logo

ASP.NET

23.8K
8.7K
19
An open source web framework for building modern web apps and services with .NET
23.8K
8.7K
+ 1
19
PROS OF ASP.NET
  • 13
    Great mvc
  • 6
    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

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

Java

105.8K
81K
3.7K
A concurrent, class-based, object-oriented, language specifically designed to have as few implementation dependencies as possible
105.8K
81K
+ 1
3.7K
PROS OF JAVA
  • 589
    Great libraries
  • 442
    Widely used
  • 400
    Excellent tooling
  • 388
    Huge amount of documentation available
  • 332
    Large pool of developers available
  • 204
    Open source
  • 200
    Excellent performance
  • 155
    Great development
  • 149
    Vast array of 3rd party libraries
  • 148
    Used for android
  • 60
    Compiled Language
  • 49
    Used for Web
  • 46
    Managed memory
  • 45
    High Performance
  • 44
    Native threads
  • 43
    Statically typed
  • 35
    Easy to read
  • 33
    Great Community
  • 29
    Reliable platform
  • 24
    Sturdy garbage collection
  • 24
    JVM compatibility
  • 21
    Cross Platform Enterprise Integration
  • 20
    Universal platform
  • 20
    Good amount of APIs
  • 18
    Great Support
  • 14
    Great ecosystem
  • 11
    Lots of boilerplate
  • 11
    Backward compatible
  • 10
    Everywhere
  • 9
    Excellent SDK - JDK
  • 7
    Static typing
  • 7
    It's Java
  • 6
    Better than Ruby
  • 6
    Portability
  • 6
    Mature language thus stable systems
  • 6
    Cross-platform
  • 6
    Long term language
  • 5
    Clojure
  • 5
    Used for Android development
  • 5
    Vast Collections Library
  • 4
    Most developers favorite
  • 4
    Old tech
  • 3
    Javadoc
  • 3
    History
  • 3
    Testable
  • 3
    Great Structure
  • 3
    Stable platform, which many new languages depend on
  • 3
    Best martial for design
  • 2
    Faster than python
  • 1
    Type Safe
CONS OF JAVA
  • 32
    Verbosity
  • 27
    NullpointerException
  • 16
    Overcomplexity is praised in community culture
  • 14
    Nightmare to Write
  • 11
    Boiler plate code
  • 8
    Classpath hell prior to Java 9
  • 6
    No REPL
  • 4
    No property
  • 2
    Non-intuitive generic implementation
  • 2
    There is not optional parameter
  • 2
    Code are too long
  • 2
    Floating-point errors
  • 1
    Returning Wildcard Types
  • 1
    Java's too statically, stronglly, and strictly typed
  • 1
    Terrbible compared to Python/Batch Perormence

related Java posts

Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 41 upvotes · 5.2M 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
Kamil Kowalski
Lead Architect at Fresha · | 28 upvotes · 1.6M 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
Python logo

Python

183.8K
153.4K
6.6K
A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
183.8K
153.4K
+ 1
6.6K
PROS OF PYTHON
  • 1.1K
    Great libraries
  • 944
    Readable code
  • 833
    Beautiful code
  • 777
    Rapid development
  • 682
    Large community
  • 425
    Open source
  • 385
    Elegant
  • 277
    Great community
  • 268
    Object oriented
  • 214
    Dynamic typing
  • 75
    Great standard library
  • 56
    Very fast
  • 51
    Functional programming
  • 42
    Scientific computing
  • 41
    Easy to learn
  • 33
    Great documentation
  • 26
    Matlab alternative
  • 25
    Productivity
  • 25
    Easy to read
  • 21
    Simple is better than complex
  • 18
    It's the way I think
  • 17
    Imperative
  • 15
    Free
  • 15
    Very programmer and non-programmer friendly
  • 14
    Powerfull language
  • 14
    Powerful
  • 13
    Fast and simple
  • 13
    Machine learning support
  • 12
    Scripting
  • 9
    Explicit is better than implicit
  • 8
    Clear and easy and powerfull
  • 8
    Unlimited power
  • 8
    Ease of development
  • 7
    Import antigravity
  • 6
    Print "life is short, use python"
  • 6
    It's lean and fun to code
  • 5
    High Documented language
  • 5
    I love snakes
  • 5
    Although practicality beats purity
  • 5
    Flat is better than nested
  • 5
    Great for tooling
  • 5
    Fast coding and good for competitions
  • 5
    There should be one-- and preferably only one --obvious
  • 5
    Python has great libraries for data processing
  • 4
    Readability counts
  • 3
    Beautiful is better than ugly
  • 3
    Multiple Inheritence
  • 3
    Great for analytics
  • 3
    CG industry needs
  • 3
    Plotting
  • 3
    Lists, tuples, dictionaries
  • 3
    Rapid Prototyping
  • 3
    Socially engaged community
  • 3
    Complex is better than complicated
  • 3
    Now is better than never
  • 2
    List comprehensions
  • 2
    Web scraping
  • 2
    Many types of collections
  • 2
    Easy to setup and run smooth
  • 2
    Generators
  • 2
    Special cases aren't special enough to break the rules
  • 2
    If the implementation is hard to explain, it's a bad id
  • 2
    If the implementation is easy to explain, it may be a g
  • 2
    Simple and easy to learn
  • 2
    Import this
  • 2
    No cruft
  • 2
    Easy to learn and use
  • 1
    Better outcome
  • 1
    Powerful language for AI
  • 1
    Should START with this but not STICK with This
  • 1
    Can understand easily who are new to programming
  • 1
    Batteries included
  • 1
    Good for hacking
  • 1
    A-to-Z
  • 1
    Only one way to do it
  • 1
    Because of Netflix
  • 1
    Pip install everything
  • 1
    It is Very easy , simple and will you be love programmi
  • 1
    Flexible and easy
  • 0
    Powerful
CONS OF PYTHON
  • 51
    Still divided between python 2 and python 3
  • 29
    Performance impact
  • 26
    Poor syntax for anonymous functions
  • 21
    GIL
  • 19
    Package management is a mess
  • 14
    Too imperative-oriented
  • 12
    Dynamic typing
  • 12
    Hard to understand
  • 10
    Very slow
  • 8
    Not everything is expression
  • 7
    Indentations matter a lot
  • 7
    Explicit self parameter in methods
  • 6
    No anonymous functions
  • 6
    Poor DSL capabilities
  • 6
    Incredibly slow
  • 6
    Requires C functions for dynamic modules
  • 5
    The "lisp style" whitespaces
  • 5
    Fake object-oriented programming
  • 5
    Hard to obfuscate
  • 5
    Threading
  • 4
    Circular import
  • 4
    The benevolent-dictator-for-life quit
  • 4
    Official documentation is unclear.
  • 4
    Lack of Syntax Sugar leads to "the pyramid of doom"
  • 4
    Not suitable for autocomplete
  • 2
    Meta classes
  • 1
    Training wheels (forced indentation)

related Python posts

Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 41 upvotes · 5.2M views

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

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

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

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

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

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

See more
Nick Parsons
Building cool things on the internet 🛠️ at Stream · | 35 upvotes · 1.7M views

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

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

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

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

#FrameworksFullStack #Languages

See more
PHP logo

PHP

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

related PHP posts

Nick Rockwell
SVP, Engineering at Fastly · | 44 upvotes · 2.1M views

When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

See more
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 26 upvotes · 2.9M views

Our whole Node.js backend stack consists of the following tools:

  • Lerna as a tool for multi package and multi repository management
  • npm as package manager
  • NestJS as Node.js framework
  • TypeScript as programming language
  • ExpressJS as web server
  • Swagger UI for visualizing and interacting with the API’s resources
  • Postman as a tool for API development
  • TypeORM as object relational mapping layer
  • JSON Web Token for access token management

The main reason we have chosen Node.js over PHP is related to the following artifacts:

  • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
  • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
  • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
  • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
See more
JavaScript logo

JavaScript

266.4K
211.5K
7.9K
Lightweight, interpreted, object-oriented language with first-class functions
266.4K
211.5K
+ 1
7.9K
PROS OF JAVASCRIPT
  • 1.6K
    Can be used on frontend/backend
  • 1.5K
    It's everywhere
  • 1.1K
    Lots of great frameworks
  • 891
    Fast
  • 739
    Light weight
  • 421
    Flexible
  • 388
    You can't get a device today that doesn't run js
  • 286
    Non-blocking i/o
  • 235
    Ubiquitousness
  • 189
    Expressive
  • 53
    Extended functionality to web pages
  • 46
    Relatively easy language
  • 44
    Executed on the client side
  • 28
    Relatively fast to the end user
  • 23
    Pure Javascript
  • 19
    Functional programming
  • 12
    Async
  • 10
    Setup is easy
  • 10
    Full-stack
  • 9
    Because I love functions
  • 9
    Its everywhere
  • 8
    Can be used in backend, frontend and DB
  • 8
    JavaScript is the New PHP
  • 8
    Like it or not, JS is part of the web standard
  • 7
    Expansive community
  • 7
    Future Language of The Web
  • 6
    Love-hate relationship
  • 6
    Easy
  • 6
    For the good parts
  • 6
    Everyone use it
  • 6
    Easy to hire developers
  • 6
    Evolution of C
  • 6
    Supports lambdas and closures
  • 6
    Agile, packages simple to use
  • 6
    Popularized Class-Less Architecture & Lambdas
  • 5
    Powerful
  • 5
    Most Popular Language in the World
  • 5
    Its fun and fast
  • 5
    No need to use PHP
  • 5
    Can be used both as frontend and backend as well
  • 5
    Photoshop has 3 JS runtimes built in
  • 5
    Versitile
  • 4
    What to add
  • 4
    Clojurescript
  • 4
    Function expressions are useful for callbacks
  • 4
    Everywhere
  • 4
    Hard not to use
  • 4
    Promise relationship
  • 4
    Scope manipulation
  • 4
    Client processing
  • 4
    Easy to make something
  • 4
    Nice
  • 4
    It's fun
  • 4
    Stockholm Syndrome
  • 4
    Can be used on frontend/backend/Mobile/create PRO Ui
  • 4
    It let's me use Babel & Typescript
  • 4
    Client side JS uses the visitors CPU to save Server Res
  • 4
    1.6K Can be used on frontend/backend
  • 3
    Because it is so simple and lightweight
  • 3
    Only Programming language on browser
  • 0
    Easy to understand
CONS OF JAVASCRIPT
  • 21
    A constant moving target, too much churn
  • 20
    Horribly inconsistent
  • 14
    Javascript is the New PHP
  • 8
    No ability to monitor memory utilitization
  • 6
    Shows Zero output in case of ANY error
  • 5
    Can be ugly
  • 4
    Thinks strange results are better than errors
  • 2
    No GitHub
  • 1
    Slow

related JavaScript 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
Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 41 upvotes · 5.2M 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
Node.js logo

Node.js

148.8K
125.6K
8.5K
A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
148.8K
125.6K
+ 1
8.5K
PROS OF NODE.JS
  • 1.4K
    Npm
  • 1.3K
    Javascript
  • 1.1K
    Great libraries
  • 1K
    High-performance
  • 801
    Open source
  • 485
    Great for apis
  • 475
    Asynchronous
  • 420
    Great community
  • 390
    Great for realtime apps
  • 295
    Great for command line utilities
  • 81
    Node Modules
  • 81
    Websockets
  • 68
    Uber Simple
  • 59
    Great modularity
  • 58
    Allows us to reuse code in the frontend
  • 42
    Easy to start
  • 35
    Great for Data Streaming
  • 32
    Realtime
  • 28
    Awesome
  • 25
    Non blocking IO
  • 18
    Can be used as a proxy
  • 17
    High performance, open source, scalable
  • 16
    Non-blocking and modular
  • 15
    Easy and Fun
  • 14
    Easy and powerful
  • 13
    Same lang as AngularJS
  • 13
    Future of BackEnd
  • 12
    Fullstack
  • 11
    Fast
  • 10
    Scalability
  • 10
    Cross platform
  • 9
    Simple
  • 8
    Mean Stack
  • 7
    Easy concurrency
  • 7
    Great for webapps
  • 6
    React
  • 6
    Friendly
  • 6
    Typescript
  • 6
    Fast, simple code and async
  • 5
    Easy to use and fast and goes well with JSONdb's
  • 5
    Fast development
  • 5
    Control everything
  • 5
    Great speed
  • 5
    Scalable
  • 5
    Its amazingly fast and scalable
  • 4
    It's fast
  • 4
    Isomorphic coolness
  • 4
    Easy to use
  • 3
    Less boilerplate code
  • 3
    Easy to learn
  • 3
    Easy
  • 3
    Great community
  • 3
    Not Python
  • 3
    Sooper easy for the Backend connectivity
  • 3
    Performant and fast prototyping
  • 3
    Blazing fast
  • 3
    TypeScript Support
  • 3
    Scales, fast, simple, great community, npm, express
  • 3
    One language, end-to-end
  • 2
    Npm i ape-updating
  • 2
    Event Driven
  • 2
    Lovely
CONS OF NODE.JS
  • 46
    Bound to a single CPU
  • 43
    New framework every day
  • 37
    Lots of terrible examples on the internet
  • 30
    Asynchronous programming is the worst
  • 23
    Callback
  • 18
    Javascript
  • 11
    Dependency hell
  • 11
    Dependency based on GitHub
  • 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 · 2.1M views

When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

See more
Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 41 upvotes · 5.2M 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

31K
27.8K
3.9K
The Web framework for perfectionists with deadlines
31K
27.8K
+ 1
3.9K
PROS OF DJANGO
  • 646
    Rapid development
  • 476
    Open source
  • 409
    Great community
  • 359
    Easy to learn
  • 268
    Mvc
  • 219
    Beautiful code
  • 212
    Elegant
  • 196
    Free
  • 195
    Great packages
  • 182
    Great libraries
  • 71
    Restful
  • 69
    Powerful
  • 68
    Comes with auth and crud admin panel
  • 65
    Great documentation
  • 62
    Great for web
  • 48
    Python
  • 38
    Great orm
  • 36
    Great for api
  • 27
    All included
  • 22
    Fast
  • 22
    Web Apps
  • 19
    Used by top startups
  • 18
    Clean
  • 17
    Easy setup
  • 16
    Sexy
  • 13
    Convention over configuration
  • 13
    ORM
  • 10
    The Django community
  • 10
    Allows for very rapid development with great libraries
  • 8
    King of backend world
  • 7
    Its elegant and practical
  • 7
    Great MVC and templating engine
  • 6
    Batteries included
  • 6
    Full stack
  • 6
    Have not found anything that it can't do
  • 6
    Fast prototyping
  • 6
    Cross-Platform
  • 6
    Mvt
  • 5
    Easy to develop end to end AI Models
  • 5
    Very quick to get something up and running
  • 5
    Easy Structure , useful inbuilt library
  • 4
    Easy
  • 4
    Many libraries
  • 4
    Great peformance
  • 4
    Easy to use
  • 4
    Modular
  • 4
    Python community
  • 3
    Just the right level of abstraction
  • 3
    Scaffold
  • 3
    Full-Text Search
  • 3
    Map
  • 3
    Zero code burden to change databases
  • 3
    Easy to change database manager
  • 1
    Node js
  • 0
    Fastapi
  • 0
    Rails
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
Laravel logo

Laravel

23.2K
19K
3.7K
A PHP Framework For Web Artisans
23.2K
19K
+ 1
3.7K
PROS OF LARAVEL
  • 529
    Clean architecture
  • 379
    Growing community
  • 357
    Composer friendly
  • 329
    Open source
  • 309
    The only framework to consider for php
  • 211
    Mvc
  • 203
    Quickly develop
  • 161
    Dependency injection
  • 150
    Application architecture
  • 138
    Embraces good community packages
  • 68
    Write less, do more
  • 63
    Orm (eloquent)
  • 61
    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
    JSON friendly
  • 22
    Modern PHP
  • 22
    Easy to learn, scalability
  • 21
    Blade Template
  • 21
    Most easy for me
  • 20
    Test-Driven
  • 20
    Beautiful
  • 14
    Security
  • 13
    Based on SOLID
  • 12
    Easy to attach Middleware
  • 12
    Cool
  • 12
    Clean Documentation
  • 11
    Convention over Configuration
  • 11
    Simple
  • 10
    Easy Request Validatin
  • 9
    Fast
  • 9
    Simpler
  • 9
    Easy to use
  • 8
    Its just wow
  • 8
    Friendly API
  • 8
    Get going quickly straight out of the box. BYOKDM
  • 8
    Laravel + Cassandra = Killer Framework
  • 7
    Simplistic , easy and faster
  • 7
    Super easy and powerful
  • 7
    Less dependencies
  • 6
    Great customer support
  • 6
    Its beautiful to code in
  • 5
    Speed
  • 5
    Easy
  • 5
    The only "cons" is wrong! No static method just Facades
  • 5
    Fast and Clarify framework
  • 5
    Active Record
  • 5
    Php7
  • 4
    Eloquent
  • 4
    Laragon
  • 4
    Composer
  • 4
    Laravel Mix
  • 4
    Minimum system requirements
  • 4
    Easy views handling and great ORM
  • 3
    Ease of use
  • 3
    Laravel Forge and Envoy
  • 3
    Laravel Horizon and Telescope
  • 3
    Laravel Passport
  • 3
    Intuitive usage
  • 3
    Cashier with Braintree and Stripe
  • 3
    Laravel Spark
  • 3
    Laravel Nova
  • 3
    Laravel casher
  • 2
    Scout
  • 2
    Rapid development
  • 1
    Deployment
CONS OF LARAVEL
  • 48
    PHP
  • 31
    Too many dependency
  • 22
    Slower than the other two
  • 17
    A lot of static method calls for convenience
  • 15
    Too many include
  • 12
    Heavy
  • 8
    Bloated
  • 7
    Laravel
  • 6
    Confusing
  • 5
    Too underrated
  • 3
    Not fast with MongoDB
  • 1
    Difficult to learn
  • 1
    Not using SOLID principles

related Laravel posts

I need to build a web application plus android and IOS apps for an enterprise, like an e-commerce portal. It will have intensive use of MySQL to display thousands (40-50k) of live product information in an interactive table (searchable, filterable), live delivery tracking. It has to be secure, as it will handle information on customers, sales, inventory. Here is the technology stack: Backend: Laravel 7 Frondend: Vue.js, React or AngularJS?

Need help deciding technology stack. Thanks.

See more
Antonio Sanchez

Back at the start of 2017, we decided to create a web-based tool for the SEO OnPage analysis of our clients' websites. We had over 2.000 websites to analyze, so we had to perform thousands of requests to get every single page from those websites, process the information and save the big amounts of data somewhere.

Very soon we realized that the initial chosen script language and database, PHP, Laravel and MySQL, was not going to be able to cope efficiently with such a task.

By that time, we were doing some experiments for other projects with a language we had recently get to know, Go , so we decided to get a try and code the crawler using it. It was fantastic, we could process much more data with way less CPU power and in less time. By using the concurrency abilites that the language has to offers, we could also do more Http requests in less time.

Unfortunately, I have no comparison numbers to show about the performance differences between Go and PHP since the difference was so clear from the beginning and that we didn't feel the need to do further comparison tests nor document it. We just switched fully to Go.

There was still a problem: despite the big amount of Data we were generating, MySQL was performing very well, but as we were adding more and more features to the software and with those features more and more different type of data to save, it was a nightmare for the database architects to structure everything correctly on the database, so it was clear what we had to do next: switch to a NoSQL database. So we switched to MongoDB, and it was also fantastic: we were expending almost zero time in thinking how to structure the Database and the performance also seemed to be better, but again, I have no comparison numbers to show due to the lack of time.

We also decided to switch the website from PHP and Laravel to JavaScript and Node.js and ExpressJS since working with the JSON Data that we were saving now in the Database would be easier.

As of now, we don't only use the tool intern but we also opened it for everyone to use for free: https://tool-seo.com

See more