21–26 of 26 posts
Earlier quoted context omitted.
Where I can see this being really useful is for people trying out GraphQL for the first time. If you already know PostgreSQL, throwing this interface over it means the GraphQL bit is the only thing you've got to learn.
Agreed. My impression is that using this in a real project is almost a non-starter, but it's a good way for trying out GraphQL.
Earlier quoted context omitted.
Agreed. My impression is that using this in a real project is almost a non-starter, but it's a good way for trying out GraphQL.
What? Why would it be a "non-starter"? It is made for being used for real, and people use it for real.
Of course, it's almost impossible to prove IRL, but still, a lot of corporations have problems with that. They want the free open source project to make them earn money, no price to pay.
Earlier quoted context omitted.
What? Why would it be a "non-starter"? It is made for being used for real, and people use it for real.
It's just that many people want to be able to use the software by doing modifications to it for their secret sauce. And they don't want to share the sauce. AGPL forces you to share it, even if you don't distribute the software: as long as you make a service with your modified version, you are legally entitled to share the modifications. Of course, it's almost impossible to prove IRL, but still, a lot of corporations…
Earlier quoted context omitted.
What? Why would it be a "non-starter"? It is made for being used for real, and people use it for real.
It's just that many people want to be able to use the software by doing modifications to it for their secret sauce. And they don't want to share the sauce. AGPL forces you to share it, even if you don't distribute the software: as long as you make a service with your modified version, you are legally entitled to share the modifications. Of course, it's almost impossible to prove IRL, but still, a lot of corporations…
This looks amazing. I can't wait to dig into the internals and play around. I've been thinking about a "Postgres-first" application design for some time, where a thin GraqhQL/REST layer sits on top, and most of the business logic lives in Postgres directly, or operates as a triggered async function (eg; AWS Lambda).
You can setup a cloudfront distribution postgres rds.
Use Postgraphql/postgrest as stateless api layer. I would use a docker container and ECS to keep it horizontally scalable.
Then just whip together a client app that consumes your api.
Earlier quoted context omitted.
Agreed. My impression is that using this in a real project is almost a non-starter, but it's a good way for trying out GraphQL.
What? Why would it be a "non-starter"? It is made for being used for real, and people use it for real.
My use of "real project" was perhaps a little unfair. What I mean is that as soon as you go beyond the simplest requirements of a GraphQL server, a solution like this is going to present more problems than it solves.