BenjieGillam

10 ms·

31.
by BenjieGillam 7y ago
Thanks for mentioning Graphile Migrate. Migrations are often the biggest issue people have with something like PostgREST and PostGraphile; I’ve used a lot of the various migration tools and Graphile Migrate is the seed of my vision for a mu
32.
by BenjieGillam 7y ago
Have you tried the PostGraphile Starter? It’s not officially released yet but you can find out more in the Discord chat #announcements channel. https://discord.gg/graphile
33.
by BenjieGillam 7y ago
Neat; happy to have inspired you!
34.
by BenjieGillam 7y ago
I wouldn't let that sway you too much; the main reason for the performance difference is that PostgREST builds the JSON response in the database and then pipes that through to the user directly (at least that's my understanding).
35.
by BenjieGillam 7y ago
I’m going to be speaking at ReactiveConf in Prague, so sadly cannot make it to SF; hopefully see you at another conference though!
36.
by BenjieGillam 7y ago
No problem; I saw 8base at one of the GraphQL conferences, looks cool. I agree: PostGraphile is intended for people who want to control their own servers (be that via serverless, containers, Heroku, or traditional servers).
37.
by BenjieGillam 7y ago
PostGraphile is not an ORM, it’s a client-facing GraphQL API designed to be consumed directly from your frontend applications (web apps, mobile apps, etc). This is why it has such powerful customisation and extension features so you can use
38.
by BenjieGillam 7y ago
I suspect many of these concerns were with PostgreSQL 9.5 and 9.6 where RLS did indeed have many performance issues. PG 10 fixed a large number of these issues, and PG11 even more. I would recommend re-evaluating RLS performance on these la
39.
by BenjieGillam 8y ago
It feels a bit misleading to say PostGraphile is "GraphQL-as-a-Service". Typically XaaS is used when there's an external service (normally hosted elsewhere) that provides this functionality; whereas PostGraphile is 100% self-
40.
by BenjieGillam 8y ago
I’m sorry you feel that way; I use PostGraphile with external APIs frequently, using makeExtendSchemaPlugin to easily add more types and resolvers to my GraphQL schema. Maybe you could go into more detail on the issues you’ve faced here so
41.
by BenjieGillam 8y ago
There’s a bit of a chicken and egg problem with that; basically you’re requiring someone to build and grow the community for free for years until it gets “big and crucial” before paying them, by which time they may well have burned out and
42.
by BenjieGillam 8y ago
PostGraphile is built on Graphile Engine which is completely backend-independent (like GraphQL itself). This is what we use in PostGraphile for the "look-ahead" functionality, allowing you to build a database/API/backend
43.
by BenjieGillam 8y ago
Thanks!
44.
by BenjieGillam 9y ago
This is PostGraphQL, we're renaming to PostGraphile with the official release of v4 which should happen in the coming months.
45.
by BenjieGillam 9y ago
Great questions! You're right with number 1: RBAC + RLS (+ custom mutation functions if you need them). For number 2, the solution is currently naive composition of SQL fragments, CTEs, and trusting PostgreSQL to find optimal solutions
46.
by BenjieGillam 9y ago
From my chat with graph.cool the other day it seems like graphql-bindings would be a very thin wrapper that also can be auto-generated from a GraphQL schema (e.g. PostGraphile), so there shouldn't be too much additional complexity, and
47.
by BenjieGillam 9y ago
You should consider talking to Johannes Schickling of graph.cool; they seem to be very interested in that sort of thing and they've got some really cool open source going on right now. Johannes is a really nice person - I'd defini
48.
by BenjieGillam 9y ago
Very similar! The project was originally inspired by PostgREST - the main difference being that it uses GraphQL as the API layer rather than REST.
49.
by BenjieGillam 9y ago
Yeah, renaming things is always painful. We're renaming the project because "GraphQL" is owned by Facebook and we don't want any trademark disputes down the line. We've mentioned the rename in a number of places but
50.
by BenjieGillam 9y ago
Hi, PostGraphile maintainer here. Excellent points! This is actually where the powerful GraphQL ecosystem comes in really handy - with functionality such as GraphQL schema stitching (e.g. graphql-weaver) you can use something like PostGraph
51.
React.js: Error boundaries merged(github.com)
2 points by BenjieGillam 11y ago|0 comments
52.
by BenjieGillam 13y ago
This couldn't have happened at a better time for the apps we're working on in the coming months! Congratulations on launching and all the best for the future :)
53.
Amazon RDS now Supports MySQL 5.6 with Memcached and Binary Log Access(aws.amazon.com)
1 points by BenjieGillam 13y ago|0 comments
54.
Quantum JavaScript?(benjiegillam.com)
3 points by BenjieGillam 13y ago|0 comments
55.
Ejecta: fast open source JS, canvas and audio on iOS(github.com)
4 points by BenjieGillam 14y ago|0 comments
56.
by BenjieGillam 14y ago
I'm inclined to believe this is legitimate research - looking up the IP address seems to check out, it's at least assigned to "Technische Universitaet Muenchen". First probe I've seen that truthfully declares itself as non-threatening.
57.
this-is-not-an-attack: SSH probe username of security researcher?(188.95.234.6)
4 points by BenjieGillam 14y ago|1 comments
58.
Webkit Inspector console.log begins supporting colours, à la Firebug(trac.webkit.org)
2 points by BenjieGillam 14y ago|0 comments
59.
by BenjieGillam 14y ago
Isn't this just the pin remapping chip that tells the device what it is (USB/HDMI/accessory/etc) and enables the cable to be plugged in either way and still use all 16 pins? http://appleinsider.com/articles/12/09/25/apples_lightning_p...
60.
by BenjieGillam 14y ago
I have results - I'm impressed with the quality of the output - especially that errors aren't cascaded! I would spend more time looking at it now but unfortunately it takes a while to load each screenshot currently. I'll check back tomorrow

More ›