Alternatives to MaxScale logo

Alternatives to MaxScale

HAProxy, ProxySQL, Slick, Sequel Pro, and PostGIS are the most popular alternatives and competitors to MaxScale.
15
14
+ 1
0

What is MaxScale and what are its top alternatives?

It is a database proxy that extends the high availability, scalability, and security of MariaDB Server while at the same time simplifying application development by decoupling it from underlying database infrastructure.
MaxScale is a tool in the Database Tools category of a tech stack.

MaxScale alternatives & related posts

related HAProxy posts

Tom Klein
Tom Klein
CEO at Gentlent · | 9 upvotes · 86.9K views
atGentlentGentlent
Git
Git
GitHub
GitHub
GitLab
GitLab
Docker
Docker
Kubernetes
Kubernetes
HAProxy
HAProxy
Varnish
Varnish
npm
npm
Visual Studio Code
Visual Studio Code

We're using Git through GitHub for public repositories and GitLab for our private repositories due to its easy to use features. Docker and Kubernetes are a must have for our highly scalable infrastructure complimented by HAProxy with Varnish in front of it. We are using a lot of npm and Visual Studio Code in our development sessions.

See more
StackShare Editors
StackShare Editors
| 5 upvotes · 141.7K views
atUber TechnologiesUber Technologies
nginx
nginx
StatsD
StatsD
HAProxy
HAProxy

The frontline API is proxied through a HAProxy load balancer with NGINX as the fronted, which also handles SSL termination. This frontline API consist of 600 stateless endpoints that join together multiple services.

As part of the Marketplace stack, engineers in this area integrate with various other internal services, including logtron to log to disk and Kafka and uber-statsd-client, the Node.js client for statsd.

See more
ProxySQL logo

ProxySQL

13
6
0
13
6
+ 1
0
A High-performance, GPL licensed MySQL proxy
    Be the first to leave a pro
    ProxySQL logo
    ProxySQL
    VS
    MaxScale logo
    MaxScale
    Slick logo

    Slick

    7.9K
    58
    0
    7.9K
    58
    + 1
    0
    Database query and access library for Scala
      Be the first to leave a pro
      Slick logo
      Slick
      VS
      MaxScale logo
      MaxScale
      Sequel Pro logo

      Sequel Pro

      239
      169
      63
      239
      169
      + 1
      63
      MySQL database management for Mac OS X
      Sequel Pro logo
      Sequel Pro
      VS
      MaxScale logo
      MaxScale
      PostGIS logo

      PostGIS

      194
      143
      28
      194
      143
      + 1
      28
      Open source spatial database
      PostGIS logo
      PostGIS
      VS
      MaxScale logo
      MaxScale
      Open PostgreSQL Monitoring logo

      Open PostgreSQL Monitoring

      136
      109
      0
      136
      109
      + 1
      0
      Oversee and Manage Your PostgreSQL Servers
        Be the first to leave a pro
        Open PostgreSQL Monitoring logo
        Open PostgreSQL Monitoring
        VS
        MaxScale logo
        MaxScale

        related Flyway posts

        Miguel Suarez
        Miguel Suarez
        Lead Developer · | 8 upvotes · 125.1K views
        atJobsrepublicJobsrepublic
        Flyway
        Flyway
        Liquibase
        Liquibase
        PostgreSQL
        PostgreSQL
        #Migration
        #Backwards-compatible

        Flyway vs Liquibase #Migration #Backwards-compatible

        We were looking for a tool to help us integrating the migration scripts as part of our Deployment. At first sight both tools look very alike, are well integrated with Spring, have a fairly frequent development activity and short release cycles.

        Liquibase puts a lot of emphasis on independence with the DB, allowing you to create the scripts on formats like JSON and YML, abstracting away from SQL, which it's also supported. Since we only work with one DB type across services we wouldn't take much advantage of this feature.

        Flyway on the other hand has the advantage on being actively working on the integration with PostgreSQL 11, for it's upcoming version 6. Provides a more extensive set of properties that allow us to define what's allowed on what's not on each different environment.

        Instead of looking for a tool that will allow us to rollback our DB changes automatically, we decided to implement backwards-compatible DB changes, for example adding a new column instead of renaming an existing one, postponing the deletion of the deprecated column until the release has been successfully installed.

        See more
        DataGrip logo

        DataGrip

        113
        53
        0
        113
        53
        + 1
        0
        A database IDE for professional SQL developers
          Be the first to leave a pro
          DataGrip logo
          DataGrip
          VS
          MaxScale logo
          MaxScale
          Liquibase logo

          Liquibase

          112
          122
          33
          112
          122
          + 1
          33
          Source control for your database
          Liquibase logo
          Liquibase
          VS
          MaxScale logo
          MaxScale

          related Liquibase posts

          Miguel Suarez
          Miguel Suarez
          Lead Developer · | 8 upvotes · 125.1K views
          atJobsrepublicJobsrepublic
          Flyway
          Flyway
          Liquibase
          Liquibase
          PostgreSQL
          PostgreSQL
          #Migration
          #Backwards-compatible

          Flyway vs Liquibase #Migration #Backwards-compatible

          We were looking for a tool to help us integrating the migration scripts as part of our Deployment. At first sight both tools look very alike, are well integrated with Spring, have a fairly frequent development activity and short release cycles.

          Liquibase puts a lot of emphasis on independence with the DB, allowing you to create the scripts on formats like JSON and YML, abstracting away from SQL, which it's also supported. Since we only work with one DB type across services we wouldn't take much advantage of this feature.

          Flyway on the other hand has the advantage on being actively working on the integration with PostgreSQL 11, for it's upcoming version 6. Provides a more extensive set of properties that allow us to define what's allowed on what's not on each different environment.

          Instead of looking for a tool that will allow us to rollback our DB changes automatically, we decided to implement backwards-compatible DB changes, for example adding a new column instead of renaming an existing one, postponing the deletion of the deprecated column until the release has been successfully installed.

          See more
          Spring Data logo

          Spring Data

          111
          68
          0
          111
          68
          + 1
          0
          Provides a consistent approach to data access – relational, non-relational, map-reduce, and beyond
            Be the first to leave a pro
            Spring Data logo
            Spring Data
            VS
            MaxScale logo
            MaxScale
            MySQL WorkBench logo

            MySQL WorkBench

            106
            58
            0
            106
            58
            + 1
            0
            A unified visual tool for database architects, developers, and DBAs
              Be the first to leave a pro
              MySQL WorkBench logo
              MySQL WorkBench
              VS
              MaxScale logo
              MaxScale
              Microsoft SQL Server Management Studio logo

              Microsoft SQL Server Management Studio

              100
              50
              0
              100
              50
              + 1
              0
              An integrated environment for managing any SQL infrastructure
                Be the first to leave a pro
                Microsoft SQL Server Management Studio logo
                Microsoft SQL Server Management Studio
                VS
                MaxScale logo
                MaxScale

                related Knex.js posts

                Tim Nolet
                Tim Nolet
                Founder, Engineer & Dishwasher at Checkly · | 20 upvotes · 379.3K views
                atChecklyHQChecklyHQ
                Heroku
                Heroku
                Docker
                Docker
                GitHub
                GitHub
                Node.js
                Node.js
                hapi
                hapi
                Vue.js
                Vue.js
                AWS Lambda
                AWS Lambda
                Amazon S3
                Amazon S3
                PostgreSQL
                PostgreSQL
                Knex.js
                Knex.js
                vuex
                vuex

                Heroku Docker GitHub Node.js hapi Vue.js AWS Lambda Amazon S3 PostgreSQL Knex.js Checkly is a fairly young company and we're still working hard to find the correct mix of product features, price and audience.

                We are focussed on tech B2B, but I always wanted to serve solo developers too. So I decided to make a $7 plan.

                Why $7? Simply put, it seems to be a sweet spot for tech companies: Heroku, Docker, Github, Appoptics (Librato) all offer $7 plans. They must have done a ton of research into this, so why not piggy back that and try it out.

                Enough biz talk, onto tech. The challenges were:

                • Slice of a portion of the functionality so a $7 plan is still profitable. We call this the "plan limits"
                • Update API and back end services to handle and enforce plan limits.
                • Update the UI to kindly state plan limits are in effect on some part of the UI.
                • Update the pricing page to reflect all changes.
                • Keep the actual processing backend, storage and API's as untouched as possible.

                In essence, we went from strictly volume based pricing to value based pricing. Here come the technical steps & decisions we made to get there.

                1. We updated our PostgreSQL schema so plans now have an array of "features". These are string constants that represent feature toggles.
                2. The Vue.js frontend reads these from the vuex store on login.
                3. Based on these values, the UI has simple v-if statements to either just show the feature or show a friendly "please upgrade" button.
                4. The hapi API has a hook on each relevant API endpoint that checks whether a user's plan has the feature enabled, or not.

                Side note: We offer 10 SMS messages per month on the developer plan. However, we were not actually counting how many people were sending. We had to update our alerting daemon (that runs on Heroku and triggers SMS messages via AWS SNS) to actually bump a counter.

                What we build is basically feature-toggling based on plan features. It is very extensible for future additions. Our scheduling and storage backend that actually runs users' monitoring requests (AWS Lambda) and stores the results (S3 and Postgres) has no knowledge of all of this and remained unchanged.

                Hope this helps anyone building out their SaaS and is in a similar situation.

                See more
                Tim Nolet
                Tim Nolet
                Founder, Engineer & Dishwasher at Checkly · | 10 upvotes · 64.3K views
                atChecklyHQChecklyHQ
                PostgreSQL
                PostgreSQL
                Heroku
                Heroku
                Heroku Postgres
                Heroku Postgres
                Node.js
                Node.js
                Knex.js
                Knex.js

                PostgreSQL Heroku Heroku Postgres Node.js Knex.js

                Last week we rolled out a simple patch that decimated the response time of a Postgres query crucial to Checkly. It quite literally went from an average of ~100ms with peaks to 1 second to a steady 1ms to 10ms.

                However, that patch was just the last step of a longer journey:

                1. I looked at what API endpoints were using which queries and how their response time grew over time. Specifically the customer facing API endpoints that are directly responsible for rendering the first dashboard page of the product are crucial.

                2. I looked at the Heroku metrics such as those reported by heroku pg:outlier and cross references that with "slowest response time" statistics.

                3. I reproduced the production situation as best as possible on a local development machine and test my hypothesis that an composite index on a uuid field and a timestampz field would reduce response times.

                This method secured the victory and we rolled out a new index last week. Response times plummeted. Read the full story in the blog post.

                See more
                phpMyAdmin logo

                phpMyAdmin

                78
                41
                3
                78
                41
                + 1
                3
                A free software, for MySQL and MariaDB
                phpMyAdmin logo
                phpMyAdmin
                VS
                MaxScale logo
                MaxScale
                GraphiQL logo

                GraphiQL

                61
                54
                4
                61
                54
                + 1
                4
                An in-browser IDE for exploring GraphQL
                GraphiQL logo
                GraphiQL
                VS
                MaxScale logo
                MaxScale

                related GraphiQL posts

                Jerome Dalbert
                Jerome Dalbert
                Senior Backend Engineer at StackShare · | 3 upvotes · 58.2K views
                GraphQL
                GraphQL
                GraphiQL
                GraphiQL
                Insomnia REST Client
                Insomnia REST Client
                #REST
                #Api

                Postman is a nice desktop #REST #API client that allows you to save requests for later use. But it does not really support GraphQL, which I use everyday at work. So it was time to look for something else.

                GraphiQL is a nice toy that has a desktop client, but you cannot save requests in any organized way. Most other clients I tried were either sluggish, didn't save requests, or didn't support cookies. Lack of cookie support is a no-no for work because we use session-based authentication in our internal API.

                Then I stumbled upon Insomnia REST Client, and it clicked! Cookies work, GraphQL support is pretty good, UI looks nice and goes straight to the point. The only thing it lacks is a schema explorer, but I can always use GraphiQL if I ever need one, which is almost never.

                Overall, I am very happy with it, and would recommend it to anyone seriously working with GraphQL. Insomnia is a godsend!

                See more
                Active Admin logo

                Active Admin

                50
                39
                12
                50
                39
                + 1
                12
                The administration framework for Ruby on Rails applications
                Active Admin logo
                Active Admin
                VS
                MaxScale logo
                MaxScale
                Android Room logo

                Android Room

                48
                43
                0
                48
                43
                + 1
                0
                Save data in a local database
                  Be the first to leave a pro
                  Android Room logo
                  Android Room
                  VS
                  MaxScale logo
                  MaxScale
                  Postico logo

                  Postico

                  43
                  30
                  12
                  43
                  30
                  + 1
                  12
                  A modern PostgreSQL client for OS X
                  Postico logo
                  Postico
                  VS
                  MaxScale logo
                  MaxScale
                  MongoDB Compass logo

                  MongoDB Compass

                  42
                  22
                  0
                  42
                  22
                  + 1
                  0
                  A GUI for MongoDB
                    Be the first to leave a pro
                    MongoDB Compass logo
                    MongoDB Compass
                    VS
                    MaxScale logo
                    MaxScale