postgrest-js VS neon

At one point, I really thought it was used in Supabase. But I guess they only wrote the js wrapper for it. https://github.com/supabase/postgrest-js

Came here to mention Hasura as well (not sure of it's popularity though) https://hasura.io/graphql/database/postgresql

Min/Max looks like it still has to be done via RPC (with sample code here) https://github.com/supabase/postgrest-js/issues/206

There's nothing wrong with this and they're pretty open about it. But the SDK they provide for direct database operations is the weakest of the ones I've used, when it should be the strongest I think. It leverages PostgREST which is a tool for auto generating REST APIs from schemas. From the README: "The goal of this library is to make an "ORM-like" restful interface."

Looks like there's an open github issue that might answer some of your questions: https://github.com/supabase/postgrest-js/issues/303

I think it’s great too. I wish they would shore up some of their existing releases though. Probably most notably, the ability to query aggregates via the officially supported route is missing: https://github.com/supabase/postgrest-js/issues/206

The workarounds suggested are not ergonomic for most use cases and it feels pretty out of place for such basic functionality to be missing in what otherwise feels like a pretty full featured product.

Their Realtime product is another example of something that languishes while new features get launched.

I haven't completely understood what you are looking for but I think Supabase could be potential useful alternative backend for you supabase.io ?

I used postgrest-js to communicate with my PostgREST endpoint. The library is easy to use and does everything for you.

yes you're right. The JS library is a thin wrapper around PostgREST's API (https://github.com/supabase/postgrest-js)

Supabase now offers a few more features which integrate with the Postgres database - File Storage (s3), Authentication, Deno Functions, and Realtime (database change listeners). Each of these services is a standalone server and each has a corresponding JS library.

"supabase-js" wraps up the modular JS libraries into a single library for convenience

* Swift Libraries are now underway thanks to @satishbabariya [2]

We still have a long way to go for mobile support, but the Apple logins is a big one. If you ship an app to the App Store with any third-party logins, you're required to enable Apple logins as well. While this sounds like a bit of over-reach, it's actually quite cool - if you use Apple login they obfuscate your email so that the 3rd party app don't get access to your personal data. Quite nice!

[0] CSV: https://github.com/supabase/postgrest-js/pull/187

If you're reading this you probably got a really steep bill from Neon after finding yourself on their "Scale" plan. If you do want to stay with Neon but avoid surprise bills then go to the Plans page and choose what you actually want.

Such is the case with Neon, a serverless Postgres service, that went generally available on April 15. Congrats Nikita Shamgunov and team on the launch. When I saw the announcement, I knew I had to try it out for myself and report back with my findings.

I want to use this as a chance to bring attention to a GitHub issue that I think would help reduce friction for Neon:

https://github.com/neondatabase/neon/issues/4989

If the Neon driver were to allow us to easily pass in a localhost connection, the development and test experience would be easier. Perhaps Neon could swap to something like this internally: https://github.com/porsager/postgres.

Having run a local dev environment connected to Neon and tests connected to Neon got in our way of adoption. We'd prefer to develop and run tests against a regular Postgres localhost database.

To the PMs of Neon, put yourself in the shoes of a new developer thinking of giving Neon a try. What changes will I have to make to my code and my development workflow?

Neon is an open source and cloud-native serverless database platform that focuses on simplicity and ease of use. It supports Postgres databases and offers built-in features like bottomless storage, autoscaling, and branching.

For MySQL, we've got PlanetScale, and for PostgreSQL, there's Neon.

8. https://neon.tech/As you might know not one tool fits all, I still have strong preferences for the following. It helps me get going faster and get things done right first time and helps in ease of maintenance.

Language: Typescript.

Migrated away when they removed the free tier, ended up using https://neon.tech/

Cool! At Neon[0], I work full time on our custom postgres proxy[1]. It's a very nice protocol to work with, although our usecase is quite a bit more complex compared to the ideas presented in the post.

Neon databases scale to zero, so the proxy needs to spin up databases on the fly. The proxy doesn't do that but it knows if the databases is running and asks our control plane to schedule it if it isn't. It's a fun service to maintain.

The biggest pain is error handling. Postgres is really bad for error messages and codes. The only available code we can use is usually protocol violation...

[0]: https://neon.tech/

Neon - PostgreSQL