Alternatives to PostgREST logo

Alternatives to PostgREST

GraphQL, Slick, Sequel Pro, PostGIS, and Spring Data are the most popular alternatives and competitors to PostgREST.
31
59
+ 1
5

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 14.2K GitHub stars and 675 GitHub forks. Here’s a link to PostgREST's open source repository on GitHub

PostgREST alternatives & related posts

related GraphQL posts

Node.js
Node.js
GraphQL
GraphQL
MongoDB
MongoDB

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
Nick Rockwell
CTO at NY Times · | 30 upvotes · 875.1K views
atThe New York TimesThe New York Times
MySQL
MySQL
PHP
PHP
React
React
Apollo
Apollo
GraphQL
GraphQL
Node.js
Node.js
Kafka
Kafka
Apache HTTP Server
Apache HTTP Server

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

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

    Sequel Pro

    254
    184
    63
    254
    184
    + 1
    63
    MySQL database management for Mac OS X
    Sequel Pro logo
    Sequel Pro
    VS
    PostgREST logo
    PostgREST
    PostGIS logo

    PostGIS

    209
    173
    29
    209
    173
    + 1
    29
    Open source spatial database
    PostGIS logo
    PostGIS
    VS
    PostgREST logo
    PostgREST
    Spring Data logo

    Spring Data

    173
    125
    0
    173
    125
    + 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
      PostgREST logo
      PostgREST
      Microsoft SQL Server Management Studio logo

      Microsoft SQL Server Management Studio

      160
      105
      0
      160
      105
      + 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
        PostgREST logo
        PostgREST
        DataGrip logo

        DataGrip

        151
        105
        0
        151
        105
        + 1
        0
        A database IDE for professional SQL developers
          Be the first to leave a pro
          DataGrip logo
          DataGrip
          VS
          PostgREST logo
          PostgREST

          related Flyway posts

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