Alternatives to Sequel Pro logo

Alternatives to Sequel Pro

Navicat, PostgreSQL, MySQL WorkBench, phpMyAdmin, and DataGrip are the most popular alternatives and competitors to Sequel Pro.
235
166
+ 1
63

What is Sequel Pro and what are its top alternatives?

Sequel Pro is a fast, easy-to-use Mac database management application for working with MySQL databases.
Sequel Pro is a tool in the Database Tools category of a tech stack.
Sequel Pro is an open source tool with 7.2K GitHub stars and 643 GitHub forks. Here’s a link to Sequel Pro's open source repository on GitHub

Sequel Pro alternatives & related posts

Navicat logo

Navicat

20
8
0
20
8
+ 1
0
A comprehensive DB tool for MySQL, MariaDB, SQL Server, SQLite, Oracle and PostgreSQL development and management.
    Be the first to leave a pro
    Navicat logo
    Navicat
    VS
    Sequel Pro logo
    Sequel Pro
    PostgreSQL logo

    PostgreSQL

    17.3K
    13.1K
    3.4K
    17.3K
    13.1K
    + 1
    3.4K
    A powerful, open source object-relational database system
    PostgreSQL logo
    PostgreSQL
    VS
    Sequel Pro logo
    Sequel Pro

    related PostgreSQL posts

    Jeyabalaji Subramanian
    Jeyabalaji Subramanian
    CTO at FundsCorner · | 24 upvotes · 348.9K views
    atFundsCornerFundsCorner
    MongoDB
    MongoDB
    PostgreSQL
    PostgreSQL
    MongoDB Stitch
    MongoDB Stitch
    Node.js
    Node.js
    Amazon SQS
    Amazon SQS
    Python
    Python
    SQLAlchemy
    SQLAlchemy
    AWS Lambda
    AWS Lambda
    Zappa
    Zappa

    Recently we were looking at a few robust and cost-effective ways of replicating the data that resides in our production MongoDB to a PostgreSQL database for data warehousing and business intelligence.

    We set ourselves the following criteria for the optimal tool that would do this job: - The data replication must be near real-time, yet it should NOT impact the production database - The data replication must be horizontally scalable (based on the load), asynchronous & crash-resilient

    Based on the above criteria, we selected the following tools to perform the end to end data replication:

    We chose MongoDB Stitch for picking up the changes in the source database. It is the serverless platform from MongoDB. One of the services offered by MongoDB Stitch is Stitch Triggers. Using stitch triggers, you can execute a serverless function (in Node.js) in real time in response to changes in the database. When there are a lot of database changes, Stitch automatically "feeds forward" these changes through an asynchronous queue.

    We chose Amazon SQS as the pipe / message backbone for communicating the changes from MongoDB to our own replication service. Interestingly enough, MongoDB stitch offers integration with AWS services.

    In the Node.js function, we wrote minimal functionality to communicate the database changes (insert / update / delete / replace) to Amazon SQS.

    Next we wrote a minimal micro-service in Python to listen to the message events on SQS, pickup the data payload & mirror the DB changes on to the target Data warehouse. We implemented source data to target data translation by modelling target table structures through SQLAlchemy . We deployed this micro-service as AWS Lambda with Zappa. With Zappa, deploying your services as event-driven & horizontally scalable Lambda service is dumb-easy.

    In the end, we got to implement a highly scalable near realtime Change Data Replication service that "works" and deployed to production in a matter of few days!

    See more
    Robert Zuber
    Robert Zuber
    CTO at CircleCI · | 22 upvotes · 218.8K views
    atCircleCICircleCI
    MongoDB
    MongoDB
    PostgreSQL
    PostgreSQL
    Redis
    Redis
    GitHub
    GitHub
    Amazon S3
    Amazon S3

    We use MongoDB as our primary #datastore. Mongo's approach to replica sets enables some fantastic patterns for operations like maintenance, backups, and #ETL.

    As we pull #microservices from our #monolith, we are taking the opportunity to build them with their own datastores using PostgreSQL. We also use Redis to cache data we’d never store permanently, and to rate-limit our requests to partners’ APIs (like GitHub).

    When we’re dealing with large blobs of immutable data (logs, artifacts, and test results), we store them in Amazon S3. We handle any side-effects of S3’s eventual consistency model within our own code. This ensures that we deal with user requests correctly while writes are in process.

    See more
    MySQL WorkBench logo

    MySQL WorkBench

    89
    40
    0
    89
    40
    + 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
      Sequel Pro logo
      Sequel Pro
      phpMyAdmin logo

      phpMyAdmin

      68
      33
      0
      68
      33
      + 1
      0
      A free software, for MySQL and MariaDB
        Be the first to leave a pro
        phpMyAdmin logo
        phpMyAdmin
        VS
        Sequel Pro logo
        Sequel Pro
        DataGrip logo

        DataGrip

        100
        44
        0
        100
        44
        + 1
        0
        A database IDE for professional SQL developers
          Be the first to leave a pro
          DataGrip logo
          DataGrip
          VS
          Sequel Pro logo
          Sequel Pro
          Slick logo

          Slick

          7.8K
          29
          0
          7.8K
          29
          + 1
          0
          Database query and access library for Scala
            Be the first to leave a pro
            Slick logo
            Slick
            VS
            Sequel Pro logo
            Sequel Pro
            PostGIS logo

            PostGIS

            186
            136
            28
            186
            136
            + 1
            28
            Open source spatial database
            PostGIS logo
            PostGIS
            VS
            Sequel Pro logo
            Sequel Pro
            Open PostgreSQL Monitoring logo

            Open PostgreSQL Monitoring

            133
            107
            0
            133
            107
            + 1
            0
            Oversee and Manage Your PostgreSQL Servers
              Be the first to leave a pro
              Open PostgreSQL Monitoring logo
              Open PostgreSQL Monitoring
              VS
              Sequel Pro logo
              Sequel Pro

              related Flyway posts

              Miguel Suarez
              Miguel Suarez
              Lead Developer · | 8 upvotes · 82.5K 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
              Liquibase logo

              Liquibase

              107
              100
              33
              107
              100
              + 1
              33
              Source control for your database
              Liquibase logo
              Liquibase
              VS
              Sequel Pro logo
              Sequel Pro

              related Liquibase posts

              Miguel Suarez
              Miguel Suarez
              Lead Developer · | 8 upvotes · 82.5K 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

              97
              58
              0
              97
              58
              + 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
                Sequel Pro logo
                Sequel Pro

                related Knex.js posts

                Tim Nolet
                Tim Nolet
                Founder, Engineer & Dishwasher at Checkly · | 19 upvotes · 270K 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 · 41K 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
                Microsoft SQL Server Management Studio logo

                Microsoft SQL Server Management Studio

                74
                32
                0
                74
                32
                + 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
                  Sequel Pro logo
                  Sequel Pro
                  DBeaver logo

                  DBeaver

                  69
                  27
                  0
                  69
                  27
                  + 1
                  0
                  A Universal Database Tool
                    Be the first to leave a pro
                    DBeaver logo
                    DBeaver
                    VS
                    Sequel Pro logo
                    Sequel Pro
                    GraphiQL logo

                    GraphiQL

                    51
                    44
                    4
                    51
                    44
                    + 1
                    4
                    An in-browser IDE for exploring GraphQL
                    GraphiQL logo
                    GraphiQL
                    VS
                    Sequel Pro logo
                    Sequel Pro

                    related GraphiQL posts

                    Jerome Dalbert
                    Jerome Dalbert
                    Senior Backend Engineer at StackShare · | 3 upvotes · 35.9K 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

                    45
                    35
                    12
                    45
                    35
                    + 1
                    12
                    The administration framework for Ruby on Rails applications
                    Active Admin logo
                    Active Admin
                    VS
                    Sequel Pro logo
                    Sequel Pro
                    Android Room logo

                    Android Room

                    34
                    31
                    0
                    34
                    31
                    + 1
                    0
                    Save data in a local database
                      Be the first to leave a pro
                      Android Room logo
                      Android Room
                      VS
                      Sequel Pro logo
                      Sequel Pro
                      TablePlus logo

                      TablePlus

                      32
                      21
                      1
                      32
                      21
                      + 1
                      1
                      Easily edit database data and structure
                      TablePlus logo
                      TablePlus
                      VS
                      Sequel Pro logo
                      Sequel Pro