Alternatives to .NET Core logo

Alternatives to .NET Core

ASP.NET, ASP.NET Core, Java, Mono, and Node.js are the most popular alternatives and competitors to .NET Core.
2.6K
2.3K
+ 1
144

What is .NET Core and what are its top alternatives?

Cross-platform (supporting Windows, macOS, and Linux) and can be used to build device, cloud, and IoT applications.
.NET Core is a tool in the Frameworks (Full Stack) category of a tech stack.
.NET Core is an open source tool with 18.1K GitHub stars and 4.6K GitHub forks. Here’s a link to .NET Core's open source repository on GitHub

Top Alternatives to .NET Core

  • ASP.NET
    ASP.NET

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

  • ASP.NET Core
    ASP.NET Core

    A free and open-source web framework, and higher performance than ASP.NET, developed by Microsoft and the community. It is a modular framework that runs on both the full .NET Framework, on Windows, and the cross-platform .NET Core. ...

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

  • Mono
    Mono

    It is a software platform designed to allow developers to easily create cross platform applications part of the .NET Foundation. It is an open source implementation of Microsoft's .NET Framework based on the ECMA standards for C# and the Common Language Runtime. ...

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

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

.NET Core alternatives & related posts

ASP.NET logo

ASP.NET

24.5K
9.1K
35
An open source web framework for building modern web apps and services with .NET
24.5K
9.1K
+ 1
35
PROS OF ASP.NET
  • 19
    Great mvc
  • 11
    Easy to learn
  • 5
    C#
CONS OF ASP.NET
  • 1
    Entity framework is very slow
  • 1
    Not highly flexible for advance Developers

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
ASP.NET Core logo

ASP.NET Core

10.3K
2.3K
1.6K
A cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux
10.3K
2.3K
+ 1
1.6K
PROS OF ASP.NET CORE
  • 131
    C#
  • 110
    Performance
  • 90
    Open source
  • 85
    NuGet
  • 81
    Easy to learn and use
  • 79
    Productive
  • 74
    Visual Studio
  • 70
    Fast
  • 67
    Fast Performance With Microservices
  • 63
    Easily Expose API
  • 61
    Cross Platform
  • 59
    Scalable
  • 58
    Rapid Development
  • 52
    Web Apps
  • 43
    Visual Studio Code
  • 42
    Easy to learn
  • 37
    Azure Integration
  • 36
    MVC
  • 33
    Professionally Developed Packages
  • 31
    Great MVC and templating engine with Razor
  • 30
    Signalr
  • 30
    Razor Pages
  • 29
    Dependency Injection
  • 25
    JetBrains Rider
  • 24
    Easy to start
  • 23
    Tooling
  • 19
    One stop shop
  • 18
    MVVM
  • 15
    Fantastic and caring community
  • 11
    Add a pro
  • 9
    High Performance
  • 8
    Linux Support
  • 3
    Native AOT
  • 2
    WASI/WAGI
  • 2
    Free
  • 2
    Integration test easy & reliable
  • 2
    Easy tooling to deploy on container
CONS OF ASP.NET CORE
  • 5
    Great Doc
  • 3
    Fast
  • 2
    Clean
  • 2
    Professionally written Nuget Packages, vs IMPORT junk
  • 1
    Long polling is difficult to implement

related ASP.NET Core posts

Nicoara Bogdan
.Net Developer at Exe Software · | 6 upvotes · 28.5K views
Shared insights
on
Next.jsNext.jsReactReactASP.NET CoreASP.NET Core

I'm looking to develop a website. My current plan is to use ASP.NET Core 5 web api for backend and React for front end. But not long ago I hear of Next.js and that it is capable to have all backend inside Next.js. If so, is it still worth using .Net + React (or some other combination of frameworks).

See more
Taimoor Mirza
Associate Software Engineer at Intech Process Automation · | 5 upvotes · 526.7K views

For context, I currently use JavaScript (React) and Python (Flask) in my daily routine.

I need your help in choosing either Spring Boot or ASP.NET Core. Both frameworks seem to have mature ecosystems. I would like to hear your thoughts on the following points:

  • Difficulty level of both frameworks
  • Level of community support
  • Career prospects i.e do Spring based jobs pay more or vice versa
  • which one will be helpful if I decide to transition towards a more specialized field like data engineering.

I am asking this because it is something that I am also exploring in parallel. I know that Python and #SQL play a huge role in big data.

See more
Java logo

Java

107.5K
83.3K
3.7K
A concurrent, class-based, object-oriented, language specifically designed to have as few implementation dependencies as possible
107.5K
83.3K
+ 1
3.7K
PROS OF JAVA
  • 591
    Great libraries
  • 444
    Widely used
  • 400
    Excellent tooling
  • 389
    Huge amount of documentation available
  • 332
    Large pool of developers available
  • 204
    Open source
  • 201
    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
    Good amount of APIs
  • 20
    Universal platform
  • 18
    Great Support
  • 14
    Great ecosystem
  • 11
    Backward compatible
  • 11
    Lots of boilerplate
  • 10
    Everywhere
  • 9
    Excellent SDK - JDK
  • 7
    Static typing
  • 7
    It's Java
  • 6
    Mature language thus stable systems
  • 6
    Better than Ruby
  • 6
    Long term language
  • 6
    Cross-platform
  • 6
    Portability
  • 5
    Clojure
  • 5
    Vast Collections Library
  • 5
    Used for Android development
  • 4
    Most developers favorite
  • 4
    Old tech
  • 3
    Javadoc
  • 3
    Stable platform, which many new languages depend on
  • 3
    History
  • 3
    Testable
  • 3
    Best martial for design
  • 3
    Great Structure
  • 2
    Faster than python
  • 2
    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.3M 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.7M 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
Mono logo

Mono

76
55
1
Open source implementation of Microsoft's .NET Framework
76
55
+ 1
1
PROS OF MONO
  • 1
    It was great, pre-dotnetcore
CONS OF MONO
    Be the first to leave a con

    related Mono posts

    Node.js logo

    Node.js

    153.4K
    129.5K
    8.5K
    A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
    153.4K
    129.5K
    + 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
      Fast, simple code and async
    • 6
      Typescript
    • 6
      Friendly
    • 6
      React
    • 5
      Fast development
    • 5
      Control everything
    • 5
      Great speed
    • 5
      Scalable
    • 5
      Easy to use and fast and goes well with JSONdb's
    • 5
      Its amazingly fast and scalable
    • 4
      Isomorphic coolness
    • 4
      It's fast
    • 4
      Easy to use
    • 3
      Not Python
    • 3
      Less boilerplate code
    • 3
      One language, end-to-end
    • 3
      Scales, fast, simple, great community, npm, express
    • 3
      TypeScript Support
    • 3
      Sooper easy for the Backend connectivity
    • 3
      Performant and fast prototyping
    • 3
      Great community
    • 3
      Easy
    • 3
      Easy to learn
    • 3
      Blazing fast
    • 2
      Lovely
    • 2
      Event Driven
    • 2
      Npm i ape-updating
    • 0
      Node
    CONS OF NODE.JS
    • 46
      Bound to a single CPU
    • 43
      New framework every day
    • 37
      Lots of terrible examples on the internet
    • 31
      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
    • 2
      No standard approach
    • 1
      Bad transitive dependency management
    • 1
      Can't read server session

    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.3M 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

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

    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.7K
    19.5K
    3.7K
    A PHP Framework For Web Artisans
    23.7K
    19.5K
    + 1
    3.7K
    PROS OF LARAVEL
    • 532
      Clean architecture
    • 380
      Growing community
    • 359
      Composer friendly
    • 329
      Open source
    • 310
      The only framework to consider for php
    • 212
      Mvc
    • 204
      Quickly develop
    • 162
      Dependency injection
    • 151
      Application architecture
    • 139
      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
      Awesome
    • 36
      Great documentation
    • 27
      Awsome, Powerfull, Fast and Rapid
    • 26
      Build Apps faster, easier and better
    • 25
      Promotes elegant coding
    • 22
      JSON friendly
    • 22
      Modern PHP
    • 22
      Eloquent ORM
    • 22
      Easy to learn, scalability
    • 21
      Most easy for me
    • 21
      Blade Template
    • 20
      Beautiful
    • 20
      Test-Driven
    • 14
      Based on SOLID
    • 14
      Security
    • 12
      Clean Documentation
    • 12
      Easy to attach Middleware
    • 12
      Cool
    • 11
      Convention over Configuration
    • 11
      Simple
    • 10
      Easy Request Validatin
    • 9
      Easy to use
    • 9
      Fast
    • 9
      Simpler
    • 8
      Its just wow
    • 8
      Laravel + Cassandra = Killer Framework
    • 8
      Get going quickly straight out of the box. BYOKDM
    • 8
      Friendly API
    • 7
      Simplistic , easy and faster
    • 7
      Super easy and powerful
    • 7
      Less dependencies
    • 6
      Its beautiful to code in
    • 6
      Great customer support
    • 5
      Minimum system requirements
    • 5
      Laravel Mix
    • 5
      Php7
    • 5
      Speed
    • 5
      Easy
    • 5
      The only "cons" is wrong! No static method just Facades
    • 5
      Fast and Clarify framework
    • 5
      Active Record
    • 4
      Laragon
    • 4
      Composer
    • 4
      Easy views handling and great ORM
    • 4
      Eloquent
    • 3
      Laravel Nova
    • 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
    • 3
      Laravel casher
    • 3
      Laravel Spark
    • 2
      Scout
    • 2
      Rapid development
    • 1
      Succint sintax
    • 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
    Android SDK logo

    Android SDK

    22.8K
    17.7K
    787
    An SDK that provides you the API libraries and developer tools necessary to build, test, and debug apps...
    22.8K
    17.7K
    + 1
    787
    PROS OF ANDROID SDK
    • 285
      Android development
    • 154
      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
      Больно
    • 2
      Free
    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 · 917.2K 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 · 775.9K 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