tango12

16 ms·

1. 151.▲
   by tango12 8y ago

   (I'm from Hasura) Well, today it is fairly dependent on postgres, but we can add more SQL backends eventually. We also leverage some neat Postgres performance tricks which would have to change depending on the database. Do you have a d
2. 152.▲
   by tango12 8y ago

   Hey, I'm from Hasura. Out of curiosity, did you face trouble trying to get something like Mongo running in the same enterprise context? Especially back when they were AGPL? We've put up an explanation reg. our AGPL licens here: h
3. 153.▲
   by tango12 8y ago

   This is cool! I like the idea of building a query through command-line "flags". We built graphqurl[1] which does tab-based autocomplete to hep the user type a complete GraphQL query (using introspection); which can get a little un
4. 154.▲
   by tango12 8y ago

   Hey! Hasura founder here :) Exactly this, we're working on adding remote schema merging into Hasura itself (kind of like AppSync) so this won't be a problem. This should be out very soon!
5. 155.▲
   by tango12 8y ago

   If you're thinking about moving databases Postgres or Postgres with TimescaleDB [1] might be an interesting option to consider. But yeah, like akerl_ said, StackOverflow seems like the right place to ask otherwise. [1]: https:/&#
6. 156.▲
   by tango12 8y ago

   Thanks. This is helpful! One question on the API contract, giving frontend teams power thing: what are your thoughts on things like firebase on the one hand and graphql on the other?
7. 157.▲
   by tango12 8y ago

   Hm...not sure why you think this goes against what you’re saying. The idea is just to make things more asynchronous and give the front end team the ability to consume async information. Also, giving the frontend team the power to query wha
8. 158.▲
   by tango12 8y ago

   In this particular case, I meant the former. But you might have workflows where the same event is delivered to multiple serverless compute things simultaneously.
9. 159.▲
   by tango12 8y ago

   Well, you could also “serverless” with kubernetes and vendor + OSS ecosystem around running containers with 0-n scaling aka serverless is also getting better. Also, GraphQL is important because it’s a convenient way for clients to consume a
10. 160.▲
    by tango12 8y ago

    We built https://github.com/hasura/graphql-engine , https://hasura.io that sets up the plumbing for this architecture with state being Postgres. There’s a lot of other tooling emerging in this direction to
11. 161.▲
    by tango12 8y ago

    Hi HN! Wrote this up based on our experiences working with early adopters of GraphQL and serverless. There have been lots of teething pains with serverless architectures and we've seen this as being a useful way of pushing business log
12. 162.▲
    by tango12 8y ago

    A 100 times this. Over the years I've realized that less that the difference between junior engineers and senior engineers is the difference between engineers who understand how to best create and deliver value for their team/proj
13. 163.▲
    JavaScript frameworks comparison(medium.com)

    5 points by tango12 8y ago|0 comments
14. 164.▲
    by tango12 8y ago

    We provide an access control layer as a part of the GraphQL engine. We took inspiration from Postgres's RLS and basically implemented it at the API layer so that the permissions/access control system is driven by your application
15. 165.▲
    by tango12 8y ago

    Hi HN! We wrote this CLI to explore migrating from Firebase to Postgres as easily as possible. We use Hasura[1] to generate the realtime GraphQL API on Postgres automatically. The CLI tool's work then mostly boils down to 2 things, whi
16. 166.▲
    by tango12 8y ago

    Or you can use serverless asynchronously only. Have a low latency container based API with min replicas and auto-scale, almost like an atomic CRUD API. Move as much to async serverless which is triggered on events.
17. 167.▲
    by tango12 8y ago

    Do you run a single instance Postgres or a cluster? What kind of failure modes have you tested if you’re running a cluster?
18. 168.▲
    Ask HN: How are you building large apps with react and GraphQL

    4 points by tango12 8y ago|0 comments
19. 169.▲
    by tango12 8y ago

    SQL could actually be an API language without needing to be wrapped in JSON/GraphQL. Building a GraphQL backend makes you deal with a GraphQL AST, parse it, process it and so on. GraphQL backends are hard to build because naive impleme
20. 170.▲
    by tango12 8y ago

    True. Unfortunately, the rest of the world that cannot afford products from the apple ecosystem will continue to suffer and they are probably highest at risk of being exploited in ways they can't fathom. Not sure if/how there&#x27
21. 171.▲
    by tango12 8y ago

    Hasura - https://github.com/hasura/graphql-engine Show HN: https://news.ycombinator.com/item?id=17540263 We'd been building the tech (realtime GraphQL on Postgres) for a while, but the HN launch g
22. 172.▲
    Reliable event triggers for webhooks on Postgres events(github.com)

    2 points by tango12 8y ago|0 comments
23. 173.▲
    Trigger webhooks/serverless on postgres events(github.com)

    2 points by tango12 8y ago|0 comments
24. 174.▲
    by tango12 8y ago

    Hi HN! We'd made an open-source component called skor [1][2] a while ago and we've now merged that work, fixed many of the issues, added a convenient UI so that triggering webhooks / serverless on specific database events tak
25. 175.▲
    Show HN: Trigger webhooks on database events (Postgres)(hasura.io)

    3 points by tango12 8y ago|1 comments
26. 176.▲
    by tango12 8y ago

    Kind of what we do underneath! We make it easy to setup and manage via a UI (or optional declarative config). And then some plumbing around retrying event delivery and similar nitty gritties.
27. 177.▲
    by tango12 8y ago

    I’m not sure about a Postgres extension. It might be a problem for a Postgres server to handle a large number of http connections in fact, so I’m not sure. We’ve built https://hasura.io which is an open source web service on top
28. 178.▲
    by tango12 8y ago

    Hi HN! We’ve put together a simple interface and system to capture and deliver Postgres events to webhooks. Key features: - Event capture is atomic and reliable - event delivery has configurable retry logic - events are instrumented with un
29. 179.▲
    by tango12 8y ago

    This. Exactly this! I think anyone with experience will realise that you can get pretty much all the benefits of GraphQL with just a more sophisticated RESTish API. There is however, one thing that I think GraphQL backends have that REST ba
30. 180.▲
    by tango12 8y ago

    This is a really nice write up/story of an approach to solve the top much data on Postgres problem. I just came across an architect in a very similar space and workload as instacart busy spending countless hours trying to move off Post