Alternatives to PHP-MVC logo

Alternatives to PHP-MVC

PHP, Spring MVC, Node.js, Django, and ASP.NET are the most popular alternatives and competitors to PHP-MVC.
103
222
+ 1
3

What is PHP-MVC and what are its top alternatives?

This project is - by intention - NOT a full framework, it's a bare-bone structure, written in purely native PHP ! The php-mvc skeleton tries to be the extremely slimmed down opposite of big frameworks like Zend2, Symfony or Laravel.
PHP-MVC is a tool in the Frameworks (Full Stack) category of a tech stack.
PHP-MVC is an open source tool with GitHub stars and GitHub forks. Here’s a link to PHP-MVC's open source repository on GitHub

Top Alternatives to PHP-MVC

  • PHP
    PHP

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

  • Spring MVC
    Spring MVC

    A Java framework that follows the Model-View-Controller design pattern and provides an elegant solution to use MVC in spring framework by the help of DispatcherServlet. ...

  • Node.js
    Node.js

    Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices. ...

  • Django
    Django

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

  • ASP.NET
    ASP.NET

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

  • Laravel
    Laravel

    It is a web application framework with expressive, elegant syntax. It attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as authentication, routing, sessions, and caching. ...

  • Android SDK
    Android SDK

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

  • Spring Boot
    Spring Boot

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

PHP-MVC alternatives & related posts

PHP logo

PHP

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

related PHP posts

Nick Rockwell
SVP, Engineering at Fastly · | 46 upvotes · 3.2M 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 · | 27 upvotes · 4.6M 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
Spring MVC logo

Spring MVC

480
515
0
A Java framework which is used to build web applications
480
515
+ 1
0
PROS OF SPRING MVC
    Be the first to leave a pro
    CONS OF SPRING MVC
      Be the first to leave a con

      related Spring MVC posts

      NIDHISH PUTHIYADATH
      Lead Software Engineer at EDIFECS · | 1 upvote · 301.6K views

      Material Design for Angular Angular 2 Node.js TypeScript Spring-Boot RxJS Microsoft SQL Server Hibernate Spring MVC

      We built our customer facing portal application using Angular frontend backed by Spring boot.

      See more
      Node.js logo

      Node.js

      190.4K
      155.1K
      8.5K
      A platform built on Chrome's JavaScript runtime for easily building fast, scalable network applications
      190.4K
      155.1K
      + 1
      8.5K
      PROS OF NODE.JS
      • 1.4K
        Npm
      • 1.3K
        Javascript
      • 1.1K
        Great libraries
      • 1K
        High-performance
      • 805
        Open source
      • 486
        Great for apis
      • 477
        Asynchronous
      • 423
        Great community
      • 390
        Great for realtime apps
      • 296
        Great for command line utilities
      • 84
        Websockets
      • 83
        Node Modules
      • 69
        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
        Future of BackEnd
      • 13
        Same lang as AngularJS
      • 12
        Fullstack
      • 11
        Fast
      • 10
        Scalability
      • 10
        Cross platform
      • 9
        Simple
      • 8
        Mean Stack
      • 7
        Great for webapps
      • 7
        Easy concurrency
      • 6
        Typescript
      • 6
        Fast, simple code and async
      • 6
        React
      • 6
        Friendly
      • 5
        Control everything
      • 5
        Its amazingly fast and scalable
      • 5
        Easy to use and fast and goes well with JSONdb's
      • 5
        Scalable
      • 5
        Great speed
      • 5
        Fast development
      • 4
        It's fast
      • 4
        Easy to use
      • 4
        Isomorphic coolness
      • 3
        Great community
      • 3
        Not Python
      • 3
        Sooper easy for the Backend connectivity
      • 3
        TypeScript Support
      • 3
        Blazing fast
      • 3
        Performant and fast prototyping
      • 3
        Easy to learn
      • 3
        Easy
      • 3
        Scales, fast, simple, great community, npm, express
      • 3
        One language, end-to-end
      • 3
        Less boilerplate code
      • 2
        Npm i ape-updating
      • 2
        Event Driven
      • 2
        Lovely
      • 1
        Creat for apis
      • 0
        Node
      CONS OF NODE.JS
      • 46
        Bound to a single CPU
      • 45
        New framework every day
      • 40
        Lots of terrible examples on the internet
      • 33
        Asynchronous programming is the worst
      • 24
        Callback
      • 19
        Javascript
      • 11
        Dependency based on GitHub
      • 11
        Dependency hell
      • 10
        Low computational power
      • 7
        Can block whole server easily
      • 7
        Callback functions may not fire on expected sequence
      • 7
        Very very Slow
      • 4
        Breaking updates
      • 4
        Unstable
      • 3
        No standard approach
      • 3
        Unneeded over complication
      • 1
        Can't read server session
      • 1
        Bad transitive dependency management

      related Node.js posts

      Nick Rockwell
      SVP, Engineering at Fastly · | 46 upvotes · 3.2M 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 · | 44 upvotes · 9.5M 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

      37K
      33.2K
      4.2K
      The Web framework for perfectionists with deadlines
      37K
      33.2K
      + 1
      4.2K
      PROS OF DJANGO
      • 669
        Rapid development
      • 486
        Open source
      • 423
        Great community
      • 378
        Easy to learn
      • 275
        Mvc
      • 231
        Beautiful code
      • 222
        Elegant
      • 205
        Free
      • 202
        Great packages
      • 193
        Great libraries
      • 78
        Restful
      • 78
        Comes with auth and crud admin panel
      • 77
        Powerful
      • 74
        Great documentation
      • 70
        Great for web
      • 56
        Python
      • 42
        Great orm
      • 40
        Great for api
      • 31
        All included
      • 27
        Fast
      • 24
        Web Apps
      • 22
        Easy setup
      • 22
        Clean
      • 20
        Used by top startups
      • 19
        Sexy
      • 18
        ORM
      • 14
        The Django community
      • 14
        Convention over configuration
      • 13
        Allows for very rapid development with great libraries
      • 11
        King of backend world
      • 10
        Great MVC and templating engine
      • 9
        Full stack
      • 7
        Batteries included
      • 7
        Its elegant and practical
      • 7
        Mvt
      • 7
        Fast prototyping
      • 6
        Very quick to get something up and running
      • 6
        Easy to develop end to end AI Models
      • 6
        Cross-Platform
      • 6
        Have not found anything that it can't do
      • 5
        Zero code burden to change databases
      • 5
        Easy Structure , useful inbuilt library
      • 5
        Python community
      • 4
        Many libraries
      • 4
        Modular
      • 4
        Easy to use
      • 4
        Easy
      • 4
        Map
      • 4
        Easy to change database manager
      • 4
        Great peformance
      • 3
        Full-Text Search
      • 3
        Just the right level of abstraction
      • 3
        Scaffold
      • 1
        Great default admin panel
      • 1
        Fastapi
      • 1
        Scalable
      • 1
        Built in common security
      • 1
        Node js
      • 1
        Gigante ta
      • 0
        Rails
      CONS OF DJANGO
      • 26
        Underpowered templating
      • 22
        Autoreload restarts whole server
      • 22
        Underpowered ORM
      • 15
        URL dispatcher ignores HTTP method
      • 10
        Internal subcomponents coupling
      • 8
        Not nodejs
      • 8
        Configuration hell
      • 7
        Admin
      • 5
        Not as clean and nice documentation like Laravel
      • 4
        Python
      • 3
        Not typed
      • 3
        Bloated admin panel included
      • 2
        Overwhelming folder structure
      • 2
        InEffective Multithreading
      • 1
        Not type safe

      related Django posts

      Dmitry Mukhin
      Engineer at Uploadcare · | 25 upvotes · 2.4M views

      Simple controls over complex technologies, as we put it, wouldn't be possible without neat UIs for our user areas including start page, dashboard, settings, and docs.

      Initially, there was Django. Back in 2011, considering our Python-centric approach, that was the best choice. Later, we realized we needed to iterate on our website more quickly. And this led us to detaching Django from our front end. That was when we decided to build an SPA.

      For building user interfaces, we're currently using React as it provided the fastest rendering back when we were building our toolkit. It’s worth mentioning Uploadcare is not a front-end-focused SPA: we aren’t running at high levels of complexity. If it were, we’d go with Ember.js.

      However, there's a chance we will shift to the faster Preact, with its motto of using as little code as possible, and because it makes more use of browser APIs. One of our future tasks for our front end is to configure our Webpack bundler to split up the code for different site sections. For styles, we use PostCSS along with its plugins such as cssnano which minifies all the code.

      All that allows us to provide a great user experience and quickly implement changes where they are needed with as little code as possible.

      See more

      Hey, so I developed a basic application with Python. But to use it, you need a python interpreter. I want to add a GUI to make it more appealing. What should I choose to develop a GUI? I have very basic skills in front end development (CSS, JavaScript). I am fluent in python. I'm looking for a tool that is easy to use and doesn't require too much code knowledge. I have recently tried out Flask, but it is kinda complicated. Should I stick with it, move to Django, or is there another nice framework to use?

      See more
      ASP.NET logo

      ASP.NET

      30.3K
      11.2K
      40
      An open source web framework for building modern web apps and services with .NET
      30.3K
      11.2K
      + 1
      40
      PROS OF ASP.NET
      • 21
        Great mvc
      • 13
        Easy to learn
      • 6
        C#
      CONS OF ASP.NET
      • 2
        Entity framework is very slow
      • 1
        C#
      • 1
        Not highly flexible for advance Developers

      related ASP.NET posts

      Greg Neumann
      Indie, Solo, Developer · | 8 upvotes · 1.4M views

      Finding the most effective dev stack for a solo developer. Over the past year, I've been looking at many tech stacks that would be 'best' for me, as a solo, indie, developer to deliver a desktop app (Windows & Mac) plus mobile - iOS mainly. Initially, Xamarin started to stand-out. Using .NET Core as the run-time, Xamarin as the native API provider and Xamarin Forms for the UI seemed to solve all issues. But, the cracks soon started to appear. Xamarin Forms is mobile only; the Windows incarnation is different. There is no Mac UI solution (you have to code it natively in Mac OS Storyboard. I was also worried how Xamarin Forms , if I was to use it, was going to cope, in future, with Apple's new SwiftUI and Google's new Fuchsia.

      This plethora of techs for the UI-layer made me reach for the safer waters of using Web-techs for the UI. Lovely! Consistency everywhere (well, mostly). But that consistency evaporates when platform issues are addressed. There are so many web frameworks!

      But, I made a simple decision. It's just me...I am clever, but there is no army of coders here. And I have big plans for a business app. How could just 1 developer go-on to deploy a decent app to Windows, iPhone, iPad & Mac OS? I remembered earlier days when I've used Microsoft's ASP.NET to scaffold - generate - loads of Code for a web-app that I needed for several charities that I worked with. What 'generators' exist that do a lot of the platform-specific rubbish, allow the necessary customisation of such platform integration and provide a decent UI?

      I've placed my colours to the Quasar Framework mast. Oh dear, that means Electron desktop apps doesn't it? Well, Ive had enough of loads of Developers saying that "the menus won't look native" or "it uses too much RAM" and so on. I've been using non-native UI-wrapped apps for ages - the date picker in Outlook on iOS is way better than the native date-picker and I'd been using it for years without getting hot under the collar about it. Developers do get so hung-up on things that busy Users hardly notice; don't you think?. As to the RAM usage issue; that's a bit true. But Users only really notice when an app uses so much RAM that the machine starts to page-out. Electron contributes towards that horizon but does not cause it. My Users will be business-users after all. Somewhat decent machines.

      Looking forward to all that lovely Vue.js around my TypeScript and all those really, really, b e a u t I f u l UI controls of Quasar Framework . Still not sure that 1 dev can deliver all that... but I'm up for trying...

      See more
      Shared insights
      on
      ASP.NETASP.NETPostgreSQLPostgreSQLLaravelLaravel

      I am looking for a new framework to learn and achieve more efficient development. I come mainly from Laravel, which greatly simplifies development, but is somewhat slow for the volumes of data that I usually handle (although very stable) and it falls far behind in terms of simultaneous connections.

      I'm looking for something that responds well to high concurrency, adapts well to server resources (cores) without the need to be concerned about consciously multi-threading or similar things, has a good ORM and friendly integration with PostgreSQL, request validation, And of course, it is scalable.

      The main use would be for API development and behind the scenes processing of large volumes of data (50M on average, although this goes hand in hand with the database and server capacity)..

      The last framework I would include but couldn't is ASP.NET MVC.

      See more
      Laravel logo

      Laravel

      27.5K
      22.7K
      3.9K
      A PHP Framework For Web Artisans
      27.5K
      22.7K
      + 1
      3.9K
      PROS OF LARAVEL
      • 553
        Clean architecture
      • 392
        Growing community
      • 370
        Composer friendly
      • 344
        Open source
      • 324
        The only framework to consider for php
      • 220
        Mvc
      • 210
        Quickly develop
      • 168
        Dependency injection
      • 156
        Application architecture
      • 143
        Embraces good community packages
      • 73
        Write less, do more
      • 71
        Orm (eloquent)
      • 66
        Restful routing
      • 57
        Database migrations & seeds
      • 55
        Artisan scaffolding and migrations
      • 41
        Great documentation
      • 40
        Awesome
      • 30
        Awsome, Powerfull, Fast and Rapid
      • 29
        Build Apps faster, easier and better
      • 28
        Eloquent ORM
      • 26
        Promotes elegant coding
      • 26
        Modern PHP
      • 26
        JSON friendly
      • 25
        Most easy for me
      • 24
        Easy to learn, scalability
      • 23
        Beautiful
      • 22
        Blade Template
      • 21
        Test-Driven
      • 15
        Security
      • 15
        Based on SOLID
      • 13
        Clean Documentation
      • 13
        Easy to attach Middleware
      • 13
        Cool
      • 12
        Simple
      • 12
        Convention over Configuration
      • 11
        Easy Request Validatin
      • 10
        Simpler
      • 10
        Fast
      • 10
        Easy to use
      • 9
        Get going quickly straight out of the box. BYOKDM
      • 9
        Its just wow
      • 8
        Laravel + Cassandra = Killer Framework
      • 8
        Simplistic , easy and faster
      • 8
        Friendly API
      • 7
        Less dependencies
      • 7
        Super easy and powerful
      • 6
        Great customer support
      • 6
        Its beautiful to code in
      • 5
        Speed
      • 5
        Eloquent
      • 5
        Composer
      • 5
        Minimum system requirements
      • 5
        Laravel Mix
      • 5
        Easy
      • 5
        The only "cons" is wrong! No static method just Facades
      • 5
        Fast and Clarify framework
      • 5
        Active Record
      • 5
        Php7
      • 4
        Ease of use
      • 4
        Laragon
      • 4
        Laravel casher
      • 4
        Easy views handling and great ORM
      • 4
        Laravel Forge and Envoy
      • 4
        Cashier with Braintree and Stripe
      • 3
        Laravel Passport
      • 3
        Laravel Spark
      • 3
        Intuitive usage
      • 3
        Laravel Horizon and Telescope
      • 3
        Laravel Nova
      • 3
        Rapid development
      • 2
        Laravel Vite
      • 2
        Scout
      • 2
        Deployment
      • 1
        Succint sintax
      CONS OF LARAVEL
      • 53
        PHP
      • 33
        Too many dependency
      • 23
        Slower than the other two
      • 17
        A lot of static method calls for convenience
      • 15
        Too many include
      • 13
        Heavy
      • 9
        Bloated
      • 8
        Laravel
      • 7
        Confusing
      • 5
        Too underrated
      • 4
        Not fast with MongoDB
      • 1
        Not using SOLID principles
      • 1
        Slow and too much big
      • 1
        Difficult to learn

      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

      26.7K
      20.1K
      799
      An SDK that provides you the API libraries and developer tools necessary to build, test, and debug apps...
      26.7K
      20.1K
      + 1
      799
      PROS OF ANDROID SDK
      • 289
        Android development
      • 155
        Necessary for android
      • 128
        Android studio
      • 86
        Mobile framework
      • 82
        Backed by google
      • 27
        Platform-tools
      • 21
        Eclipse + adt plugin
      • 5
        Powerful, simple, one stop environment
      • 3
        Free
      • 3
        Больно
      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 · 1M 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 · 913.2K views

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

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

        See more
        Spring Boot logo

        Spring Boot

        25.2K
        22.9K
        1K
        Create Spring-powered, production-grade applications and services with absolute minimum fuss
        25.2K
        22.9K
        + 1
        1K
        PROS OF SPRING BOOT
        • 149
          Powerful and handy
        • 134
          Easy setup
        • 128
          Java
        • 90
          Spring
        • 85
          Fast
        • 46
          Extensible
        • 37
          Lots of "off the shelf" functionalities
        • 32
          Cloud Solid
        • 26
          Caches well
        • 24
          Productive
        • 24
          Many receipes around for obscure features
        • 23
          Modular
        • 23
          Integrations with most other Java frameworks
        • 22
          Spring ecosystem is great
        • 21
          Auto-configuration
        • 21
          Fast Performance With Microservices
        • 18
          Community
        • 17
          Easy setup, Community Support, Solid for ERP apps
        • 15
          One-stop shop
        • 14
          Easy to parallelize
        • 14
          Cross-platform
        • 13
          Easy setup, good for build erp systems, well documented
        • 13
          Powerful 3rd party libraries and frameworks
        • 12
          Easy setup, Git Integration
        • 5
          It's so easier to start a project on spring
        • 4
          Kotlin
        • 1
          Microservice and Reactive Programming
        • 1
          The ability to integrate with the open source ecosystem
        CONS OF SPRING BOOT
        • 23
          Heavy weight
        • 18
          Annotation ceremony
        • 13
          Java
        • 11
          Many config files needed
        • 5
          Reactive
        • 4
          Excellent tools for cloud hosting, since 5.x
        • 1
          Java 😒😒

        related Spring Boot posts

        Praveen Mooli
        Engineering Manager at Taylor and Francis · | 18 upvotes · 3.8M views

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

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

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

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

        See more

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

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

        See more