Alternatives to PostgREST logo

Alternatives to PostgREST

GraphQL, Slick, Spring Data, DataGrip, and Microsoft SQL Server Management Studio are the most popular alternatives and competitors to PostgREST.
51
105
+ 1
8

What is PostgREST and what are its top alternatives?

PostgREST serves a fully RESTful API from any existing PostgreSQL database. It provides a cleaner, more standards-compliant, faster API than you are likely to write from scratch.
PostgREST is a tool in the Database Tools category of a tech stack.
PostgREST is an open source tool with GitHub stars and GitHub forks. Here’s a link to PostgREST's open source repository on GitHub

Top Alternatives to PostgREST

  • GraphQL
    GraphQL

    GraphQL is a data query language and runtime designed and used at Facebook to request and deliver data to mobile and web apps since 2012. ...

  • Slick
    Slick

    It is a modern database query and access library for Scala. It allows you to work with stored data almost as if you were using Scala collections while at the same time giving you full control over when a database access happens and which data is transferred. ...

  • Spring Data
    Spring Data

    It makes it easy to use data access technologies, relational and non-relational databases, map-reduce frameworks, and cloud-based data services. This is an umbrella project which contains many subprojects that are specific to a given database. ...

  • DataGrip
    DataGrip

    A cross-platform IDE that is aimed at DBAs and developers working with SQL databases. ...

  • Microsoft SQL Server Management Studio
    Microsoft SQL Server Management Studio

    It is an integrated environment for managing any SQL infrastructure, from SQL Server to Azure SQL Database. It provides tools to configure, monitor, and administer instances of SQL Server and databases. Use it to deploy, monitor, and upgrade the data-tier components used by your applications, as well as build queries and scripts. ...

  • DBeaver
    DBeaver

    It is a free multi-platform database tool for developers, SQL programmers, database administrators and analysts. Supports all popular databases: MySQL, PostgreSQL, SQLite, Oracle, DB2, SQL Server, Sybase, Teradata, MongoDB, Cassandra, Redis, etc. ...

  • Liquibase
    Liquibase

    Liquibase is a leading open-source tool for database schema change management. Liquibase helps teams track, version, and deploy database schema and logic changes so they can automate their database code process with their app code process. ...

  • PostGIS
    PostGIS

    PostGIS is a spatial database extender for PostgreSQL object-relational database. It adds support for geographic objects allowing location queries to be run in SQL. ...

PostgREST alternatives & related posts

GraphQL logo

GraphQL

26.4K
21.7K
298
A data query language and runtime
26.4K
21.7K
+ 1
298
PROS OF GRAPHQL
  • 73
    Schemas defined by the requests made by the user
  • 62
    Will replace RESTful interfaces
  • 60
    The future of API's
  • 48
    The future of databases
  • 12
    Self-documenting
  • 11
    Get many resources in a single request
  • 5
    Ask for what you need, get exactly that
  • 4
    Query Language
  • 3
    Evolve your API without versions
  • 3
    Fetch different resources in one request
  • 3
    Type system
  • 2
    GraphiQL
  • 2
    Ease of client creation
  • 2
    Easy setup
  • 1
    Good for apps that query at build time. (SSR/Gatsby)
  • 1
    Backed by Facebook
  • 1
    Easy to learn
  • 1
    "Open" document
  • 1
    Better versioning
  • 1
    Standard
  • 1
    1. Describe your data
  • 1
    Fast prototyping
CONS OF GRAPHQL
  • 3
    Hard to migrate from GraphQL to another technology
  • 3
    More code to type.
  • 1
    All the pros sound like NFT pitches
  • 1
    Works just like any other API at runtime
  • 1
    Takes longer to build compared to schemaless.

related GraphQL posts

Shared insights
on
Node.jsNode.jsGraphQLGraphQLMongoDBMongoDB

I just finished the very first version of my new hobby project: #MovieGeeks. It is a minimalist online movie catalog for you to save the movies you want to see and for rating the movies you already saw. This is just the beginning as I am planning to add more features on the lines of sharing and discovery

For the #BackEnd I decided to use Node.js , GraphQL and MongoDB:

  1. Node.js has a huge community so it will always be a safe choice in terms of libraries and finding solutions to problems you may have

  2. GraphQL because I needed to improve my skills with it and because I was never comfortable with the usual REST approach. I believe GraphQL is a better option as it feels more natural to write apis, it improves the development velocity, by definition it fixes the over-fetching and under-fetching problem that is so common on REST apis, and on top of that, the community is getting bigger and bigger.

  3. MongoDB was my choice for the database as I already have a lot of experience working on it and because, despite of some bad reputation it has acquired in the last months, I still believe it is a powerful database for at least a very long list of use cases such as the one I needed for my website

See more
Nick Rockwell
SVP, Engineering at Fastly · | 44 upvotes · 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
Slick logo

Slick

9K
954
0
Database query and access library for Scala
9K
954
+ 1
0
PROS OF SLICK
    Be the first to leave a pro
    CONS OF SLICK
      Be the first to leave a con

      related Slick posts

      Spring Data logo

      Spring Data

      536
      347
      0
      Provides a consistent approach to data access – relational, non-relational, map-reduce, and beyond
      536
      347
      + 1
      0
      PROS OF SPRING DATA
        Be the first to leave a pro
        CONS OF SPRING DATA
          Be the first to leave a con

          related Spring Data 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
          DataGrip logo

          DataGrip

          440
          490
          14
          A database IDE for professional SQL developers
          440
          490
          + 1
          14
          PROS OF DATAGRIP
          • 4
            Works on Linux, Windows and MacOS
          • 2
            Wide range of DBMS support
          • 1
            Code completion
          • 1
            Generate ERD
          • 1
            Quick-fixes using keyboard shortcuts
          • 1
            Code analysis
          • 1
            Database introspection on 21 different dbms
          • 1
            Export data using a variety of formats using open api
          • 1
            Import data
          • 1
            Diff viewer
          CONS OF DATAGRIP
            Be the first to leave a con

            related DataGrip posts

            Microsoft SQL Server Management Studio logo

            Microsoft SQL Server Management Studio

            420
            339
            0
            An integrated environment for managing any SQL infrastructure
            420
            339
            + 1
            0
            PROS OF MICROSOFT SQL SERVER MANAGEMENT STUDIO
              Be the first to leave a pro
              CONS OF MICROSOFT SQL SERVER MANAGEMENT STUDIO
                Be the first to leave a con

                related Microsoft SQL Server Management Studio posts

                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
                DBeaver logo

                DBeaver

                373
                490
                56
                A Universal Database Tool
                373
                490
                + 1
                56
                PROS OF DBEAVER
                • 17
                  Free
                • 11
                  Platform independent
                • 8
                  Automatic driver download
                • 6
                  Import-Export Data
                • 4
                  Simple to use
                • 4
                  Wide range of DBMS support
                • 4
                  Move data between databases
                • 1
                  SAP Hana DB support
                • 1
                  Themes
                CONS OF DBEAVER
                  Be the first to leave a con

                  related DBeaver posts

                  Manikandan Shanmugam
                  Software Engineer at Blitzscaletech Software Solution · | 4 upvotes · 278.2K views
                  Shared insights
                  on
                  AzureDataStudioAzureDataStudioDBeaverDBeaver

                  Which tools are preferred if I choose to work on more data side? Which one is good if I decide to work on web development? I'm using DBeaver and am now considering a move to AzureDataStudio to break the monotony while working. I would like to hear your opinion. Which one are you using, and what are the things you are missing in dbeaver or data studio.

                  See more
                  Liquibase logo

                  Liquibase

                  357
                  550
                  60
                  Easily track, version & deploy database changes
                  357
                  550
                  + 1
                  60
                  PROS OF LIQUIBASE
                  • 18
                    Great database tool
                  • 17
                    Many DBs supported
                  • 10
                    Easy setup
                  • 6
                    Database independent migration scripts
                  • 4
                    Unique open source tool
                  • 3
                    Database version controller
                  • 1
                    Precondition checking
                  • 1
                    Supports NoSQL and Graph DBs
                  CONS OF LIQUIBASE
                  • 4
                    No vendor specifics in XML format - needs workarounds
                  • 4
                    Documentation is disorganized

                  related Liquibase posts

                  Miguel Suarez

                  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
                  Shared insights
                  on
                  FlywayFlywayLiquibaseLiquibase

                  All the DB deployments in our current organization are manual. We want to automate them. We are leaning toward Liquibase since it has versioning and rollbacks. Is Flyway better or Liquibase?

                  See more
                  PostGIS logo

                  PostGIS

                  330
                  339
                  30
                  Open source spatial database
                  330
                  339
                  + 1
                  30
                  PROS OF POSTGIS
                  • 25
                    De facto GIS in SQL
                  • 5
                    Good Documentation
                  CONS OF POSTGIS
                    Be the first to leave a con

                    related PostGIS posts