Alternatives to XAMPP logo

Alternatives to XAMPP

MAMP, MySQL WorkBench, Docker, Bitnami, and NGINX are the most popular alternatives and competitors to XAMPP.
107
220
+ 1
6

What is XAMPP and what are its top alternatives?

It consists mainly of the Apache HTTP Server, MariaDB database, and interpreters for scripts written in the PHP and Perl programming languages.
XAMPP is a tool in the Web Servers category of a tech stack.

Top Alternatives to XAMPP

  • MAMP
    MAMP

    It can be installed under macOS and Windows with just a few clicks. It provides them with all the tools they need to run WordPress on their desktop PC for testing or development purposes, for example. It doesn't matter if you prefer Apache or Nginx or if you want to work with PHP, Python, Perl or Ruby. ...

  • MySQL WorkBench
    MySQL WorkBench

    It enables a DBA, developer, or data architect to visually design, model, generate, and manage databases. It includes everything a data modeler needs for creating complex ER models, forward and reverse engineering, and also delivers key features for performing difficult change management and documentation tasks that normally require much time and effort. ...

  • Docker
    Docker

    The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere ...

  • Bitnami
    Bitnami

    Our library provides trusted virtual machines for every major development stack and open source server application, ready to run in your infrastructure. ...

  • NGINX
    NGINX

    nginx [engine x] is an HTTP and reverse proxy server, as well as a mail proxy server, written by Igor Sysoev. According to Netcraft nginx served or proxied 30.46% of the top million busiest sites in Jan 2018. ...

  • Apache HTTP Server
    Apache HTTP Server

    The Apache HTTP Server is a powerful and flexible HTTP/1.1 compliant web server. Originally designed as a replacement for the NCSA HTTP Server, it has grown to be the most popular web server on the Internet. ...

  • Microsoft IIS
    Microsoft IIS

    Internet Information Services (IIS) for Windows Server is a flexible, secure and manageable Web server for hosting anything on the Web. From media streaming to web applications, IIS's scalable and open architecture is ready to handle the most demanding tasks. ...

  • Apache Tomcat
    Apache Tomcat

    Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse range of industries and organizations. ...

XAMPP alternatives & related posts

MAMP logo

MAMP

53
113
2
A free, local server environment
53
113
+ 1
2
PROS OF MAMP
  • 1
    Comes with PHP and phpmyadmin preinstalled
  • 1
    Great Support of Native Languages
CONS OF MAMP
    Be the first to leave a con

    related MAMP posts

    Helfried Plenk
    Senior Partner at IBS IT-DL GmbH · | 1 upvote · 126K views
    Shared insights
    on
    MAMPMAMPXAMPPXAMPPJoomla!Joomla!

    installing a local Joomla! 3.9 website for testing - I already downloaded an installed XAMPP - when now reading some other docs I found mentioned MAMP ... have I to change?

    See more
    MySQL WorkBench logo

    MySQL WorkBench

    317
    546
    22
    A unified visual tool for database architects, developers, and DBAs
    317
    546
    + 1
    22
    PROS OF MYSQL WORKBENCH
    • 6
      Simple
    • 5
      Easy to use
    • 5
      Free
    • 4
      Clean UI
    • 2
      Administration and monitoring module
    CONS OF MYSQL WORKBENCH
      Be the first to leave a con

      related MySQL WorkBench posts

      I'm learning SQL thru UDEMY and I'm trying to DL My SQL onto my machine, but when I get to the terminal, that's where I encounter my issues- nothing can be found. If I use SQLPro Studio for the course, is it better? I ask because MySQL WorkBench integrates with SQLPro Studio. I just want to get certified and start working again.

      See more
      Kelsey Doolittle

      We have a 138 row, 1700 column database likely to grow at least a row and a column every week. We are mostly concerned with how user-friendly the graphical management tools are. I understand MySQL has MySQL WorkBench, and Microsoft SQL Server has Microsoft SQL Server Management Studio. We have about 6 months to migrate our Excel database to one of these DBMS, and continue (hopefully manually) importing excel files from then on. Any tips appreciated!

      See more
      Docker logo

      Docker

      131.3K
      104.1K
      3.8K
      Enterprise Container Platform for High-Velocity Innovation.
      131.3K
      104.1K
      + 1
      3.8K
      PROS OF DOCKER
      • 823
        Rapid integration and build up
      • 688
        Isolation
      • 518
        Open source
      • 505
        Testa­bil­i­ty and re­pro­ducibil­i­ty
      • 459
        Lightweight
      • 217
        Standardization
      • 184
        Scalable
      • 105
        Upgrading / down­grad­ing / ap­pli­ca­tion versions
      • 87
        Security
      • 84
        Private paas environments
      • 33
        Portability
      • 25
        Limit resource usage
      • 16
        Game changer
      • 15
        I love the way docker has changed virtualization
      • 13
        Fast
      • 11
        Concurrency
      • 7
        Docker's Compose tools
      • 5
        Easy setup
      • 5
        Fast and Portable
      • 4
        Because its fun
      • 3
        Makes shipping to production very simple
      • 2
        It's dope
      • 2
        Highly useful
      • 1
        Very easy to setup integrate and build
      • 1
        Package the environment with the application
      • 1
        Does a nice job hogging memory
      • 1
        Open source and highly configurable
      • 1
        Simplicity, isolation, resource effective
      • 1
        MacOS support FAKE
      • 1
        Its cool
      • 1
        Docker hub for the FTW
      • 1
        HIgh Throughput
      CONS OF DOCKER
      • 8
        New versions == broken features
      • 6
        Unreliable networking
      • 6
        Documentation not always in sync
      • 4
        Moves quickly
      • 3
        Not Secure

      related Docker posts

      Simon Reymann
      Senior Fullstack Developer at QUANTUSflow Software GmbH · | 29 upvotes · 4.2M views

      Our whole DevOps stack consists of the following tools:

      • GitHub (incl. GitHub Pages/Markdown for Documentation, GettingStarted and HowTo's) for collaborative review and code management tool
      • Respectively Git as revision control system
      • SourceTree as Git GUI
      • Visual Studio Code as IDE
      • CircleCI for continuous integration (automatize development process)
      • Prettier / TSLint / ESLint as code linter
      • SonarQube as quality gate
      • Docker as container management (incl. Docker Compose for multi-container application management)
      • VirtualBox for operating system simulation tests
      • Kubernetes as cluster management for docker containers
      • Heroku for deploying in test environments
      • nginx as web server (preferably used as facade server in production environment)
      • SSLMate (using OpenSSL) for certificate management
      • Amazon EC2 (incl. Amazon S3) for deploying in stage (production-like) and production environments
      • PostgreSQL as preferred database system
      • Redis as preferred in-memory database/store (great for caching)

      The main reason we have chosen Kubernetes over Docker Swarm is related to the following artifacts:

      • Key features: Easy and flexible installation, Clear dashboard, Great scaling operations, Monitoring is an integral part, Great load balancing concepts, Monitors the condition and ensures compensation in the event of failure.
      • Applications: An application can be deployed using a combination of pods, deployments, and services (or micro-services).
      • Functionality: Kubernetes as a complex installation and setup process, but it not as limited as Docker Swarm.
      • Monitoring: It supports multiple versions of logging and monitoring when the services are deployed within the cluster (Elasticsearch/Kibana (ELK), Heapster/Grafana, Sysdig cloud integration).
      • Scalability: All-in-one framework for distributed systems.
      • Other Benefits: Kubernetes is backed by the Cloud Native Computing Foundation (CNCF), huge community among container orchestration tools, it is an open source and modular tool that works with any OS.
      See more
      Tymoteusz Paul
      Devops guy at X20X Development LTD · | 23 upvotes · 5.1M views

      Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

      It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

      I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

      We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

      If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

      The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

      Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

      See more
      Bitnami logo

      Bitnami

      124
      173
      6
      The App Store for Server Software
      124
      173
      + 1
      6
      PROS OF BITNAMI
      • 6
        Cloud Management
      CONS OF BITNAMI
        Be the first to leave a con

        related Bitnami posts

        NGINX logo

        NGINX

        99.2K
        48.7K
        5.5K
        A high performance free open source web server powering busiest sites on the Internet.
        99.2K
        48.7K
        + 1
        5.5K
        PROS OF NGINX
        • 1.4K
          High-performance http server
        • 895
          Performance
        • 727
          Easy to configure
        • 606
          Open source
        • 529
          Load balancer
        • 287
          Scalability
        • 286
          Free
        • 223
          Web server
        • 174
          Simplicity
        • 135
          Easy setup
        • 29
          Content caching
        • 20
          Web Accelerator
        • 14
          Capability
        • 13
          Fast
        • 11
          High-latency
        • 11
          Predictability
        • 7
          Reverse Proxy
        • 6
          Supports http/2
        • 5
          The best of them
        • 4
          Enterprise version
        • 4
          Lots of Modules
        • 4
          Great Community
        • 3
          Reversy Proxy
        • 3
          High perfomance proxy server
        • 3
          Streaming media
        • 3
          Embedded Lua scripting
        • 3
          Streaming media delivery
        • 2
          Lightweight
        • 2
          saltstack
        • 2
          Fast and easy to set up
        • 2
          Slim
        • 1
          Narrow focus. Easy to configure. Fast
        • 1
          Blash
        • 1
          Ingress controller
        • 1
          GRPC-Web
        • 1
          Virtual hosting
        • 1
          Along with Redis Cache its the Most superior
        • 0
          A
        CONS OF NGINX
        • 8
          Advanced features require subscription

        related NGINX posts

        Recently I have been working on an open source stack to help people consolidate their personal health data in a single database so that AI and analytics apps can be run against it to find personalized treatments. We chose to go with a #containerized approach leveraging Docker #containers with a local development environment setup with Docker Compose and nginx for container routing. For the production environment we chose to pull code from GitHub and build/push images using Jenkins and using Kubernetes to deploy to Amazon EC2.

        We also implemented a dashboard app to handle user authentication/authorization, as well as a custom SSO server that runs on Heroku which allows experts to easily visit more than one instance without having to login repeatedly. The #Backend was implemented using my favorite #Stack which consists of FeathersJS on top of Node.js and ExpressJS with PostgreSQL as the main database. The #Frontend was implemented using React, Redux.js, Semantic UI React and the FeathersJS client. Though testing was light on this project, we chose to use AVA as well as ESLint to keep the codebase clean and consistent.

        See more
        Gabriel Pa
        Shared insights
        on
        TraefikTraefikNGINXNGINX
        at

        We switched to Traefik so we can use the REST API to dynamically configure subdomains and have the ability to redirect between multiple servers.

        We still use nginx with a docker-compose to expose the traffic from our APIs and TCP microservices, but for managing routing to the internet Traefik does a much better job

        The biggest win for naologic was the ability to set dynamic configurations without having to restart the server

        See more
        Apache HTTP Server logo

        Apache HTTP Server

        60.9K
        19.5K
        1.4K
        The most popular web server on the Internet since April 1996
        60.9K
        19.5K
        + 1
        1.4K
        PROS OF APACHE HTTP SERVER
        • 478
          Web server
        • 305
          Most widely-used web server
        • 218
          Virtual hosting
        • 148
          Fast
        • 138
          Ssl support
        • 45
          Since 1996
        • 28
          Asynchronous
        • 5
          Robust
        • 4
          Proven over many years
        • 1
          Mature
        • 1
          Perfect Support
        • 1
          Perfomance
        • 0
          Many available modules
        • 0
          Many available modules
        CONS OF APACHE HTTP SERVER
        • 3
          Hard to set up

        related Apache HTTP Server posts

        Tim Abbott
        Shared insights
        on
        NGINXNGINXApache HTTP ServerApache HTTP Server
        at

        We've been happy with nginx as part of our stack. As an open source web application that folks install on-premise, the configuration system for the webserver is pretty important to us. I have a few complaints (e.g. the configuration syntax for conditionals is a pain), but overall we've found it pretty easy to build a configurable set of options (see link) for how to run Zulip on nginx, both directly and with a remote reverse proxy in front of it, with a minimum of code duplication.

        Certainly I've been a lot happier with it than I was working with Apache HTTP Server in past projects.

        See more
        Marcel Kornegoor
        Shared insights
        on
        NGINXNGINXApache HTTP ServerApache HTTP Server

        nginx or Apache HTTP Server that's the question. The best choice depends on what it needs to serve. In general, Nginx performs better with static content, where Apache and Nginx score roughly the same when it comes to dynamic content. Since most webpages and web-applications use both static and dynamic content, a combination of both platforms may be the best solution.

        Since both webservers are easy to deploy and free to use, setting up a performance or feature comparison test is no big deal. This way you can see what solutions suits your application or content best. Don't forget to look at other aspects, like security, back-end compatibility (easy of integration) and manageability, as well.

        A reasonably good comparison between the two can be found in the link below.

        See more
        Microsoft IIS logo

        Microsoft IIS

        13.4K
        6.1K
        234
        A web server for Microsoft Windows
        13.4K
        6.1K
        + 1
        234
        PROS OF MICROSOFT IIS
        • 82
          Great with .net
        • 53
          I'm forced to use iis
        • 27
          Use nginx
        • 18
          Azure integration
        • 14
          Best for ms technologyes ms bullshit
        • 10
          Fast
        • 6
          Performance
        • 6
          Reliable
        • 4
          Powerful
        • 3
          Webserver
        • 3
          Simple to configure
        • 2
          Easy setup
        • 1
          Охуенный
        • 1
          Shipped with Windows Server
        • 1
          Ssl integration
        • 1
          1
        • 1
          Security
        • 1
          I am not forced to use iis anymore :)
        CONS OF MICROSOFT IIS
        • 1
          Had to stuck on MS stack

        related Microsoft IIS posts

        I am currently in school for computer science and am doing a class project about web servers. Our assignment is to research and select one of these web servers. Could you please let me know which one you would choose among NGINX, Microsoft IIS, and Apache HTTP Server and why?

        See more
        Apache Tomcat logo

        Apache Tomcat

        13.3K
        9.6K
        201
        An open source software implementation of the Java Servlet and JavaServer Pages technologies
        13.3K
        9.6K
        + 1
        201
        PROS OF APACHE TOMCAT
        • 79
          Easy
        • 72
          Java
        • 49
          Popular
        • 1
          Spring web
        CONS OF APACHE TOMCAT
        • 1
          Blocking - each http request block a thread

        related Apache Tomcat posts

        Остап Комплікевич

        I need some advice to choose an engine for generation web pages from the Spring Boot app. Which technology is the best solution today? 1) JSP + JSTL 2) Apache FreeMarker 3) Thymeleaf Or you can suggest even other perspective tools. I am using Spring Boot, Spring Web, Spring Data, Spring Security, PostgreSQL, Apache Tomcat in my project. I have already tried to generate pages using jsp, jstl, and it went well. However, I had huge problems via carrying already created static pages, to jsp format, because of syntax. Thanks.

        See more

        Java Spring JUnit

        Apache HTTP Server Apache Tomcat

        MySQL

        See more