Alternatives to .NET logo

Alternatives to .NET

ASP.NET, Java, Python, PHP, and JavaScript are the most popular alternatives and competitors to .NET.
5.2K
3.9K
+ 1
1.7K

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 15.8K GitHub stars and 4K 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

20K
5.5K
7
An open source web framework for building modern web apps and services with .NET
20K
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

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

    Java

    80.8K
    59.4K
    3.5K
    A concurrent, class-based, object-oriented, language specifically designed to have as few implementation dependencies as possible
    80.8K
    59.4K
    + 1
    3.5K
    PROS OF JAVA
    • 576
      Great libraries
    • 436
      Widely used
    • 396
      Excellent tooling
    • 380
      Huge amount of documentation available
    • 329
      Large pool of developers available
    • 198
      Open source
    • 194
      Excellent performance
    • 150
      Great development
    • 144
      Used for android
    • 143
      Vast array of 3rd party libraries
    • 54
      Compiled Language
    • 46
      Used for Web
    • 43
      Managed memory
    • 42
      Native threads
    • 41
      High Performance
    • 36
      Statically typed
    • 32
      Easy to read
    • 30
      Great Community
    • 26
      Reliable platform
    • 23
      JVM compatibility
    • 23
      Sturdy garbage collection
    • 19
      Cross Platform Enterprise Integration
    • 18
      Universal platform
    • 16
      Good amount of APIs
    • 16
      Great Support
    • 11
      Lots of boilerplate
    • 10
      Backward compatible
    • 10
      Great ecosystem
    • 9
      Everywhere
    • 7
      Excellent SDK - JDK
    • 6
      Mature language thus stable systems
    • 5
      Cross-platform
    • 5
      Portability
    • 5
      Better than Ruby
    • 5
      Static typing
    • 5
      It's Java
    • 5
      Clojure
    • 4
      Vast Collections Library
    • 4
      Long term language
    • 4
      Old tech
    • 3
      Best martial for design
    • 3
      Great Structure
    • 3
      Most developers favorite
    • 3
      Stable platform, which many new languages depend on
    • 3
      Used for Android development
    • 2
      Testable
    • 1
      Javadoc
    CONS OF JAVA
    • 29
      Verbosity
    • 24
      NullpointerException
    • 15
      Overcomplexity is praised in community culture
    • 14
      Nightmare to Write
    • 10
      Boiler plate code
    • 8
      Classpath hell prior to Java 9
    • 6
      No REPL
    • 4
      No property
    • 2
      Code are too long
    • 2
      There is not optional parameter
    • 2
      Floating-point errors
    • 1
      Terrbible compared to Python/Batch Perormence
    • 1
      Java's too statically, stronglly, and strictly typed
    • 1
      Non-intuitive generic implementation
    • 1
      Returning Wildcard Types

    related Java posts

    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
    Kamil Kowalski
    Lead Architect at Fresha · | 27 upvotes · 934.1K 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

    131K
    105.2K
    6.5K
    A clear and powerful object-oriented programming language, comparable to Perl, Ruby, Scheme, or Java.
    131K
    105.2K
    + 1
    6.5K
    PROS OF PYTHON
    • 1.1K
      Great libraries
    • 927
      Readable code
    • 817
      Beautiful code
    • 768
      Rapid development
    • 671
      Large community
    • 418
      Open source
    • 379
      Elegant
    • 268
      Great community
    • 261
      Object oriented
    • 209
      Dynamic typing
    • 70
      Great standard library
    • 52
      Very fast
    • 48
      Functional programming
    • 35
      Scientific computing
    • 33
      Easy to learn
    • 30
      Great documentation
    • 25
      Matlab alternative
    • 23
      Productivity
    • 22
      Easy to read
    • 19
      Simple is better than complex
    • 17
      It's the way I think
    • 17
      Imperative
    • 15
      Very programmer and non-programmer friendly
    • 14
      Powerful
    • 14
      Free
    • 13
      Fast and simple
    • 13
      Powerfull language
    • 12
      Scripting
    • 9
      Machine learning support
    • 9
      Explicit is better than implicit
    • 8
      Unlimited power
    • 8
      Ease of development
    • 7
      Import antigravity
    • 7
      Clear and easy and powerfull
    • 6
      It's lean and fun to code
    • 6
      Print "life is short, use python"
    • 5
      Flat is better than nested
    • 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
    • 5
      High Documented language
    • 5
      I love snakes
    • 5
      Although practicality beats purity
    • 5
      Great for tooling
    • 4
      Readability counts
    • 3
      CG industry needs
    • 3
      Beautiful is better than ugly
    • 3
      Multiple Inheritence
    • 3
      Complex is better than complicated
    • 3
      Great for analytics
    • 3
      Socially engaged community
    • 3
      Rapid Prototyping
    • 3
      Lists, tuples, dictionaries
    • 3
      Plotting
    • 2
      Generators
    • 2
      Simple and easy to learn
    • 2
      Import this
    • 2
      No cruft
    • 2
      Easy to learn and use
    • 2
      List comprehensions
    • 2
      Special cases aren't special enough to break the rules
    • 2
      Now is better than never
    • 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
    • 1
      Many types of collections
    • 1
      Better outcome
    • 1
      Batteries included
    • 1
      Ys
    • 1
      Good
    • 1
      Pip install everything
    • 1
      Easy to setup and run smooth
    • 1
      Because of Netflix
    • 1
      Flexible and easy
    • 1
      Web scraping
    • 1
      Should START with this but not STICK with This
    • 1
      Powerful language for AI
    • 1
      It is Very easy , simple and will you be love programmi
    • 1
      Only one way to do it
    • 1
      A-to-Z
    • 0
      Pro
    • 0
      Powerful
    CONS OF PYTHON
    • 50
      Still divided between python 2 and python 3
    • 27
      Performance impact
    • 26
      Poor syntax for anonymous functions
    • 19
      Package management is a mess
    • 19
      GIL
    • 13
      Too imperative-oriented
    • 12
      Hard to understand
    • 11
      Dynamic typing
    • 9
      Very slow
    • 8
      Not everything is expression
    • 7
      Explicit self parameter in methods
    • 7
      Indentations matter a lot
    • 6
      Poor DSL capabilities
    • 6
      No anonymous functions
    • 6
      Requires C functions for dynamic modules
    • 5
      Threading
    • 5
      The "lisp style" whitespaces
    • 5
      Hard to obfuscate
    • 4
      Fake object-oriented programming
    • 4
      Incredibly slow
    • 4
      Lack of Syntax Sugar leads to "the pyramid of doom"
    • 4
      The benevolent-dictator-for-life quit
    • 3
      Official documentation is unclear.
    • 3
      Circular import
    • 3
      Not suitable for autocomplete
    • 1
      Training wheels (forced indentation)
    • 1
      Meta classes

    related Python posts

    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
    Nick Parsons
    Director of Developer Marketing at Stream · | 35 upvotes · 1.3M 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

    104.5K
    49.4K
    4.5K
    A popular general-purpose scripting language that is especially suited to web development
    104.5K
    49.4K
    + 1
    4.5K
    PROS OF PHP
    • 941
      Large community
    • 804
      Open source
    • 757
      Easy deployment
    • 481
      Great frameworks
    • 384
      The best glue on the web
    • 232
      Continual improvements
    • 180
      Good old web
    • 141
      Web foundation
    • 131
      Community packages
    • 123
      Tool support
    • 32
      Used by wordpress
    • 30
      Excellent documentation
    • 25
      Used by Facebook
    • 23
      Because of Symfony
    • 18
      Dynamic Language
    • 14
      Awesome Language and easy to implement
    • 13
      Very powerful web language
    • 13
      Cheap hosting
    • 13
      Fast development
    • 10
      Composer
    • 9
      Because of Laravel
    • 9
      Easy to learn
    • 9
      Flexibility, syntax, extensibility
    • 7
      Worst popularity quality ratio
    • 7
      Easiest deployment
    • 7
      Readable Code
    • 7
      Fastestest Time to Version 1.0 Deployments
    • 7
      Short development lead times
    • 6
      Fast
    • 6
      Most of the web uses it
    • 6
      Faster then ever
    • 5
      Open source and large community
    • 4
      I have no choice :(
    • 4
      Easy to learn, a big community, lot of frameworks
    • 4
      Cheap to own
    • 4
      Simple, flexible yet Scalable
    • 4
      Easy to use and learn
    • 3
      Great developer experience
    • 3
      Large community, easy setup, easy deployment, framework
    • 3
      Is like one zip of air
    • 3
      Open source and great framework
    • 3
      Has the best ecommerce(Magento,Prestashop,Opencart,etc)
    • 2
      FFI
    • 2
      Walk away
    • 2
      Safe the planet
    • 2
      Hard not to use
    • 2
      Fault tolerance
    • 2
      Interpreted at the run time
    • 2
      Great flexibility. From fast prototyping to large apps
    • 2
      Used by STOMT
    CONS OF PHP
    • 19
      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 · | 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
    Simon Reymann
    Senior Fullstack Developer at QUANTUSflow Software GmbH · | 24 upvotes · 1.7M 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

    192.5K
    147.2K
    7.7K
    Lightweight, interpreted, object-oriented language with first-class functions
    192.5K
    147.2K
    + 1
    7.7K
    PROS OF JAVASCRIPT
    • 1.6K
      Can be used on frontend/backend
    • 1.5K
      It's everywhere
    • 1.1K
      Lots of great frameworks
    • 884
      Fast
    • 733
      Light weight
    • 411
      Flexible
    • 376
      You can't get a device today that doesn't run js
    • 279
      Non-blocking i/o
    • 229
      Ubiquitousness
    • 184
      Expressive
    • 48
      Extended functionality to web pages
    • 42
      Relatively easy language
    • 39
      Executed on the client side
    • 24
      Relatively fast to the end user
    • 20
      Pure Javascript
    • 15
      Functional programming
    • 8
      Async
    • 6
      JavaScript is the New PHP
    • 6
      Because I love functions
    • 6
      Full-stack
    • 6
      Setup is easy
    • 5
      Expansive community
    • 5
      Its everywhere
    • 5
      Can be used in backend, frontend and DB
    • 5
      Future Language of The Web
    • 5
      Like it or not, JS is part of the web standard
    • 4
      Popularized Class-Less Architecture & Lambdas
    • 4
      Supports lambdas and closures
    • 4
      Evolution of C
    • 4
      For the good parts
    • 4
      Easy to hire developers
    • 4
      Everyone use it
    • 4
      Love-hate relationship
    • 3
      Everywhere
    • 3
      Promise relationship
    • 3
      Agile, packages simple to use
    • 3
      What to add
    • 3
      Easy to make something
    • 3
      Nice
    • 3
      Only Programming language on browser
    • 3
      Because it is so simple and lightweight
    • 3
      Can be used on frontend/backend/Mobile/create PRO Ui
    • 3
      Function expressions are useful for callbacks
    • 3
      Photoshop has 3 JS runtimes built in
    • 3
      No need to use PHP
    • 3
      Versitile
    • 3
      Most Popular Language in the World
    • 3
      Can be used both as frontend and backend as well
    • 3
      Easy
    • 3
      Clojurescript
    • 3
      Stockholm Syndrome
    • 3
      It let's me use Babel & Typescript
    • 3
      Client side JS uses the visitors CPU to save Server Res
    • 3
      Its fun and fast
    • 3
      1.6K Can be used on frontend/backend
    • 3
      Powerful
    • 3
      Scope manipulation
    • 3
      Hard not to use
    • 3
      Client processing
    • 3
      It's fun
    • 1
      Acoperișul 0757604335
    • 1
      JavaScript j.s
    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 · | 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
    Node.js logo

    Node.js

    108.7K
    88.4K
    8.3K
    A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
    108.7K
    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
    Laravel logo

    Laravel

    18.5K
    14.4K
    3.4K
    A PHP Framework For Web Artisans
    18.5K
    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