tango12

48 ms·

181.
by tango12 8y ago
Should be very easy for heroku to add serverless containers then. Their cold-starts for their free tier is a few seconds and works quite well.
182.
by tango12 8y ago
So this is different from running docker containers on heroku because heroku has 1 to n autoscaling but not 0 to n? What are the other fundamental differences?
183.
by tango12 8y ago
Sorry for the shameless plug, but I wrote this blogpost talking about something very similar: https://blog.hasura.io/why-not-use-a-json-dsl-instead-of-gra... The main edge over REST I think, is schema introspection and cons
184.
by tango12 8y ago
Hi HN. We built this when we realised we needed a few nifty bash scripts that need to talk to a GraphQL endpoint, especially piping subscription events to run a bash command. We also use it as a node library from some lambda functions and
185.
by tango12 8y ago
I think they are. I do see a lot of twitter posts by them talking about the rise of serverless. https://twitter.com/digitalocean/status/1017529341742403586
186.
by tango12 8y ago
Might not be that easy because only postgres can take a few hundreds of connections which won't work out if you have a few thousands of serverless functions? No persistent connection pools.
187.
by tango12 8y ago
Got it! Thanks for the note, and we should be able to make this better very soon.
188.
by tango12 8y ago
Thanks :) We're adding docs for enums as we speak. What did you find lacking around the many-to-many?
189.
by tango12 8y ago
True! We actually do support this via triggers at the moment; but exposing UDFs directly is on our roadmap too.
190.
by tango12 8y ago
Roughly 30% of the code in the server code is the compiler logic.
191.
by tango12 8y ago
For Heroku: https://docs.hasura.io/1.0/graphql/manual/deployment/heroku/... For Docker: https://docs.hasura.io/1.0/graphql/manual/deployment/docker/...
192.
by tango12 8y ago
Yes and yes. 1. https://docs.hasura.io/1.0/graphql/manual/migrations/enable-... 2. For UUID just do what you would normally do. We don’t have it on the column drop down but you can create the table via
193.
by tango12 8y ago
I think it depends on how much business logic you have in your REST API layer. If you can get away with using a turnkey solution like hasura with the right access control rules or by adding schema stitching then it would save a lot of effor
194.
by tango12 8y ago
Oops! GitHub is down :( We're on https://hasura.io too.
195.
by tango12 8y ago
Well it depends on your app. Technically, you have to rebuild your app to speak GraphQL to the frontend instead of REST. Internally, your GraphQL resolvers (like URL handlers) would then do similar work with using QuerySets as you're d
196.
by tango12 8y ago
Bugger! Sorry for the inconvenience. We're updating the docs now to make this easier to navigate too. EDIT: Docs updated, we'll keep improving it too :)
197.
by tango12 8y ago
Broadly similar projects! The emphasis of Hasura is to make it seamless to work with existing databases. The primary difference is how authorization is handled. In Postgraphile, you map your application roles to Postgres users and define po
198.
by tango12 8y ago
We're adding support for JWT soon too which should prevent this overhead for applications that support JWT. But basically the idea here is to be equivalent to session cache hit. Another deployment pattern is to make everything go throu
199.
by tango12 8y ago
There could be 2 ways to solve that specific problem of sending a welcome email: 1) Write a GraphQL schema stitching gateway, that can write a custom mutation that delegates to another API (or GraphQL API) to write to the database, or write
200.
by tango12 8y ago
It's in an early preview right now, and we should have something in a week or two! Just going through some performance and security checks over the next few days. Do feel free reach out to us via discord if you'd like to take it f
201.
by tango12 8y ago
So cool! Please do reach out to us on discord [1] if you have any questions whatsoever :) 1: https://discord.gg/vBPpJkS
202.
by tango12 8y ago
Apparently the facebook team (and others in production I'm guessing) addresses some of this by only having a whitelisted set of queries in production. So you get the GraphQL flexibility during development, but a effectively a static se
203.
by tango12 8y ago
Ah! That's interesting. We didn't intend for Hasura to be something like a boilerplate that you would modify. Mostly because it's harder to work with upstream changes when you work with OSS software like that unless it'
204.
by tango12 8y ago
Hm...Haskell was an important initial choice for us because of our team's comfort with the language and also because it's neat to implement parsers and compilers. The Hasura engine is essentially a GraphQL to SQL compiler :) I&#x2
205.
by tango12 8y ago
Haha, yes we do this get this a lot! We're also planning to release a lot of cool GraphQL OSS stuff for the haskell community because of our work over the last year.
206.
by tango12 8y ago
Hi HN! Super happy to announce the first open-source release of the Hasura GraphQL engine. This is a standalone service that gives you GraphQL on Postgres. It comes with fine-grained access control that can integrate with any auth provider.
207.
Show HN: Hasura – Fast, instant GraphQL APIs on Postgres(github.com)
382 points by tango12 8y ago|103 comments
208.
by tango12 8y ago
Hi HN! Super happy to announce the first open-source release of the Hasura GraphQL engine. This is a standalone service that gives you GraphQL on Postgres. It comes with fine-grained access control that can integrate with any auth provide
209.
Show HN: Hasura: Instant GraphQL APIs on New or Existing Postgres(hasura.io)
25 points by tango12 8y ago|2 comments
210.
by tango12 8y ago
Where is your Kubernetes running? If you're using a managed kubernetes vendor you might as well use their managed postgres offering if they have one. From my experience, if you're running a MVP/toy-app type setup with a singl

More ›