tango12

9 ms·

31.
by tango12 4y ago
(from Hasura) Scaling subscriptions is hard, but we work with our users/customers at scale to make sure settings are tweaked correctly. We have users running 100k - 1M concurrent users in production for live-event type platforms. It&#x
32.
by tango12 4y ago
Hasura CEO here. Totally hear you. We're working on a new serverless infrastructure layer that'll make the pricing better for users compared to a DIY API server or to a self-hosted Hasura. It's a significant engineering lift
33.
by tango12 4y ago
Hm…ideally your remote schema can return one or more product ids and then you can create a relationship back to the model from Postgres. Link to docs: https://hasura.io/docs/latest/remote-schemas/remote-relati
34.
by tango12 4y ago
Hasura CEO here. If you're trying or evaluating using hasura (or nhost) along with Yugabyte / Cockroach feel free to reach out (email in bio). Happy to have our team help with any architecture or benchmarking things you might run
35.
by tango12 4y ago
Haven’t looked at the internals or the API, but I think for starters, Hasura is designed for working on any Postgres including ones that have existing data, especially modern Postgres offerings (crunchy, alloy db, neon, Aurora, cosmos Postg
36.
by tango12 4y ago
Hasura supports multiple data-sources and creating relationships across multiple data sources. Sources can be databases (postgres family, sql-server, big-query currently, and as we add support for new databases) or REST APIs or GraphQL APIs
37.
by tango12 4y ago
Yep. Exactly this. Our focus (Hasura) is on the last mile so that innovations on the data side (eg: materialize, ksql, timescale continuous aggregates) are “just obvious” to start building applications and services against.
38.
by tango12 4y ago
Has anyone come across neat tools for load-testing streaming APIs? We used https://github.com/hasura/graphql-bench and a set of scripts to monitor runtime characteristics of Hasura and Postgres, and reconciliation to m
39.
by tango12 4y ago
Streaming data to clients at the edge (apps or services) is a hard problem. We built an approach that keeps Postgres at the center and allows clients to consume a stream of data that is already in Postgres without any additional moving part
40.
Streaming data in Postgres to 1M clients with GraphQL(github.com)
192 points by tango12 4y ago|73 comments
41.
GraphQL streaming API with built-in authorization for Postgres(github.com)
3 points by tango12 4y ago|0 comments
42.
by tango12 4y ago
We recently added a streaming GraphQL API to Hasura to allow clients to easily consume data from Postgres as a stream. There are solutions to ingest and store a large amount of data or a stream of data. However, once this data has been ca
43.
Show HN: Instant streaming GraphQL APIs with built-in authorization for Postgres(github.com)
6 points by tango12 4y ago|0 comments
44.
by tango12 5y ago
Would love to see benchmarks! :) But just for clarity in the discussion thread here, Hasura also compiles to a single query when only Postgres is being hit and I'd expect performance to be quite similar... Ofcourse, if the GraphQL quer
45.
by tango12 5y ago
(from hasura) With Hasura, if you need want some server-side logic to be written away as an API, you could try 2 approaches: 1. Write a REST/GraphQL API in your favourite framework and bring them in as Actions/Remote-Schemas in Ha
46.
by tango12 5y ago
Noted! The CLI (esp. the new configv3), splits the metadata into modular YAML files for much easier config/review etc so that makes things easier. There's still more work to do here to make this easier. Another option, if you&#x27
47.
by tango12 5y ago
Hey folks! HasuraCon our annual user conference is happening today - virtual, free and recorded for posterity ofcourse. :) There's a tonne of stuff talking about work happening in the Hasura engine, use-cases, best practices and patte
48.
by tango12 5y ago
That's fair. :) What were some of the authz pieces you struggled with?
49.
by tango12 5y ago
(from Hasura) We want Hasura to be a self-serve API for your data, so that the API is entirely managed and as a developer you can focus entirely on your domain's data and logic. That said, we're not a 100% there for all use-cases
50.
by tango12 5y ago
Hey! We released 2.0-beta.2 this week and we're planning on releasing 2.0-stable on Mon/Tue. Sorry, I know it took a while, but we had to make sure we could make the upgrade path non-breaking given it was a massive release and thi
51.
by tango12 5y ago
Thanks! Could you point us to the docs you were looking at for the auth0 integration?
52.
by tango12 5y ago
Query-plan caching is built-in and here's a docs link for response caching: https://hasura.io/docs/latest/graphql/cloud/response-caching...
53.
by tango12 5y ago
@nicoburns: Yes, this is something that we've been thinking about, but we haven't put a spec together yet. Could you open a github issue with a rough proposal of how you'd like to specify this information? For example: at a s
54.
by tango12 5y ago
In general, and for SQL Server specifically, our intent was to add great support (low footprint, works out of the box) in a way that doesn't need DDL or write access to the underlying database. This becomes super useful for folks build
55.
by tango12 5y ago
That already works! :) Postgres was the first database we added support for! https://hasura.io/docs/2.0/graphql/core/databases/postgres/i...
56.
by tango12 5y ago
Yes! We announced experimental support earlier and here's the new spec we're implementing that will support all databases and remote schemas too. https://github.com/hasura/graphql-engine/issues/6991
57.
by tango12 5y ago
(from Hasura) I've been wanting to try out a thing and use Neo4j + Postgres simultaneously. Use Postgres for data, Neo4j for relationships and graph-y queries. Has anyone tried that? Would love any notes/pointers! Join data across
58.
Hasura GraphQL Engine and SQL Server(github.com)
182 points by tango12 5y ago|83 comments
59.
by tango12 6y ago
<3 thank you! Recently, we’ve been super excited about exploring the idea of GraphQL as almost an intermediate step in the API lifecycle. This helps bring certain benefits of GraphQL to other domains - esp non internally owned frontend a
60.
by tango12 6y ago
Bummed to have not received an email about what's happening and why from the Google team. Has anyone on a "platinum"/"enterprise" google workspace plan received any relevant communication about what's happ

More ›