dsandip
Joined 10 years ago
Karma
13
Submissions
8
Member since
Dec 5
Recent submissions
Comment · 4 years ago
Comment · 4 years ago
FD: I work at hasura and work with users/customers.
Fair point about the DB scaling but not sure if everyone is going to run into this issue. Also, lots of solutions are emerging for this specific problem (with different trade-offs of course) like distributed databases (crunchy, YugaByte, Spanner, etc.). Most folks I work with get by with a reasonably sized DB and some read replicas.
Not a GraphQL problem though IMO.
Comment · 4 years ago
As a recent transplant to the US, this looks like a fun way to get my road trip plans going :). Thank you for this!
Comment · 9 years ago
Essentially, a declarative configuration for infra is what you are getting at. You can take this further, using containers and orchestration tech, to abstract your application behind a declarative configuration making it infra agnostic (as it should be iMO). Obviously, not getting locked into any cloud provider services is a pre-requisite for this. Check out such an implementation here[1](full disclosure - I work here))
[1]: https://docs.hasura.io/0.14/ref/project-configuration-and-st...
Comment · 9 years ago
We[1] have seen a fair number of requests for managed services as devs claim that "we don't have the time or skills to maintain these open source components" (quoting verbatim from a request on Intercom). I don't think this is about having open source substitutes in all the cases. Personally not a fan of how/where the build vs. buy debate is playing out here.
[1]: https://hasura.io
Comment · 9 years ago
Agree with most of the points you made. I remember the amount of effort my team in an ad-tech co. spent distributing load across multiple providers/regions to bring down latency and add redundancy. The larger point is that the ecosystem needs to enable this by product-ifying this (a data abstraction layer that is smart enough to put the right data in the right place at the right time).
Seeing some feedback on GraphQL - Hasura has had support for converting templated GraphQL into RESTish endpoints (with Open API Spec docs if needed). We are planning to do the same for this streaming API as well - does anyone have good examples of existing REST/RESTish endpoints that something similar?