Closed shahidhk closed 1 year ago
Still a work-in-progress, but I am using it to build a social media map to follow Pro cyclists around the world.
www.procyclingmap.tech
The new spatial predicates from #1735 may come in handy.
Hey @shahidhk ,
We are using it in production since today for Sently 🎉
We migrated our huge set of data from Firebase to Postgres with Hasura because of all the limitations of Firebase. It's a great move for us and I really like Hasura.
For authentication, we are using the custom claim of Firebase. I am certainly going to write in the next weeks a blog post about migrating a stack from angular/firebase to angular/hasura.
Thanks for all and keep going 🚀
We're migrating from Prisma => Graphql Engine for some use cases that prisma was not handling. KintoHub should be in production in the next 60 days.
Hey @shahidhk
Currently under development with the graphql engine. The graphql engine is attractive and powerfull.
But my team is developing another authentication server. It would be nice if we could develop an authentication server quickly using the graphql engine
Currently developing it as a POC here @ Honeywell. Love it so far, just need to find a good multi tenant approach right now
Using it at a start up. https://www.nomad-go.com/
@Disturbing Why are you moving from Prisma to Hasura? I've also decided to use Hasura instead of Prisma (I'm new with both). Keep going.
I also developing one system based on Hasura. I'm moving from Strapi to Hasura.
@Disturbing Why are you moving from Prisma to Hasura? I've also decided to use Hasura instead of Prisma (I'm new with both). Keep going.
Two main issues:
1) Scaling is not out of the box / simple / with Prisma. Docs are limited and although the feature is there, but has dependencies like rabbitmq, etc. 2) Subscriptions only work if you're 100% on graphql. If a service adds/creates/modifies a record at the DB level, Hasura successfully dispatches an update event to graphql subscriptions when prisma does not. When you're working in a Frontend <> Backend <> Devops world, still speaking directly to the DB is important.
Last but not least, speaking to the team / community wise is much better so far.
Many thank your anwser. It clear my hesitate
Adding some more names from our public wiki:
Cherre: Cherre’s data fusion platform helps organizations focus on solutions and answers instead of real estate data collection and resolution
Innovation Labs @ BBVA: Deeptracy, the Open Security Dependency Analyser Service [github]
Plutus: With the Plutus Debit card you can make worldwide contactless payments and earn a reward on the Blockchain
Sail CI: Cloud native continuous integration platform with unlimited concurrency as standard
Zeppelin: Internally used by the growth team to build MVP and new products
Fastcup: An eSports matchmaking & tournament platform for popular games - CS:GO, CS 1.6, Dota2, PUBG, etc.
We are using it at Totely for business to customer interactions
I'm using Hasura for all data on https://www.comparajogos.com.br, a website for board game prices comparisons across Brazilian stores.
We are using graphql-engine as our main inventory system for art and charity auctions at https://de-pury.com/
We are using Hasura in ARTEMIS, which is an open-source tool that monitors BGP (i.e., the inter-domain routing control plane of the Internet) for potential hijacking attempts against a network's own prefixes. The system detects such attacks within seconds, enabling immediate mitigation. We are using graphql queries and the hasura graphql engine API so that our ARTEMIS frontend can get real-time information from the main Postgres DB (BGP updates, BGP hijack events, db stats, etc.). Read more about it here: https://github.com/FORTH-ICS-INSPIRE/artemis
Have several side projects/future SaaS apps currently running on Heroku. Moved from graphcool/prisma a while ago and very pleased so far.
Using at a startup project to provide some Queries for a B2B web dashboard with many "list/show my org's
We have a quite big GraphQL API (Apollo) already and we stitch Hasura into it with Apollo schema stitching (rather than stitching existing API to hasura, for example).
My opinion so far:
using as backend in electron js App
WIP headless CMS https://github.com/arxpoetica/stallion
WIP (6 weeks ETA) sales platform. Also multiple internal projects. Will update when public
We launched our realtime location sharing app for cab drivers this week. It's a simple android application with a graphQL-postgres backend. We used the Hasura GraphQL Engine, and it amazingly simplified and accelerated our development efforts! We were able to easily support our first 500 users on a Heroku free tier. Can't thank you enough for this.
prototyping business matching app with
I'm building an e-commerce site powered by Hasura.
Front-end VueJS. Back-end NestJS, with a sprinkling of AWS Lambda.
We're using Hasura at Prefect to power parts of our Cloud backend. We were able to replace an internal GraphQL-to-SQL compiler in just a few days, and have built some useful tooling on top of Hasura, including a Python ORM. When things calm down, we'll look at open-sourcing it in case others find it as useful as we have!
We are using Hasura for Sketch.sh. It's a platform for sharing interactive OCaml/ReasonML code snippets. The whole project is OSS.
Hasura GraphQL Engine and related micro-services have been running for more than 8 months without any interventions from my part. Even though HGE is still marked at alpha version, I have to say it's extremely stable and production ready
Using Hasura at our startup Dot Dot Data. About to go live with our first app in another couple of weeks. It is a mobile app (built with Flutter) for rewarding clients for frequent visits to your business. Our entire database logic is handled by Hasura. We are hosting on Heroku and using Firebase for user authentication and event-based triggers.
I plan to use Hasura going forward, for the aforementioned startup or any other project I have a say in.
My startup boozer.bar is using hasura. We have p2p and group chat, so subscription and all sort of queries are used extensively.
There are some tricky parts like field level access, but hasura simplifies your development life. I used AWS Amplify and reimplemented to hasura in 1 week total with additional features, so it's pretty neat
We, at Lineup Ninja, are happily using Hasura. I have authored a couple of blog posts on the topic on dev.to.
We use Ember on the Frontend and a bunch of AWS stuff including Cognito for auth.
We reached the point where direct postgres connections from all our apps was just wrong. Moving forward we needed an API. I'm writing a golang client library for my company to replace all of our standard jack-c/pgx functionality. I'm just in testing now, but the library is sound. It opens Hasura up for some real backend Go stuff. I'm excited.
I've launched my app at the production URL.... procyclingmap.com
PostGIS + TimeScaleDB + Hasura Custom GraphQL queries/endpoints has made it easy to get the latest posts with their locations.
I should give a shout out to @Zeit for their now service and NextJS framework: https://github.com/zeit/next.js, as well as @jgthms for his Bulma CSS framework: https://bulma.io/
My Kindergarten Management System is nearly to be launched. All system is:
Hey, The team asked us to post about our use case. We're not using GraphQL yet but Hasura looked really promising (but ended up missing a core feature)
Basically, we run a multitenant SaaS and use standard REST. We're rolling out more and more reporting features and REST is not convenient for these at all. We looked at Hasura, thinking we could calculate the reports as views and use Hasura to expose them via GraphQL without incurring the boilerplate and fragility our current set up leads to.
So far so good, what we were missing is support for multitenancy. We'd like to be able to route to different postgres databases / instances based on request headers, but that doesn't seem supported (can't find the issue now).
We don't want to run an instance for each tenant though we may end up doing that.
Migrating an old rest api to hasura. Having difficulties with auth setup that works with old system used but for the graphql engine experience, this was awesome.
Thanks, Cezar
Hey, The team asked us to post about our use case. We're not using GraphQL yet but Hasura looked really promising (but ended up missing a core feature)
Basically, we run a multitenant SaaS and use standard REST. We're rolling out more and more reporting features and REST is not convenient for these at all. We looked at Hasura, thinking we could calculate the reports as views and use Hasura to expose them via GraphQL without incurring the boilerplate and fragility our current set up leads to.
So far so good, what we were missing is support for multitenancy. We'd like to be able to route to different postgres databases / instances based on request headers, but that doesn't seem supported (can't find the issue now).
We don't want to run an instance for each tenant though we may end up doing that.
Have you looked into schema stitching?
We are using hasura for a large scale Cybersecurity effort. We have used hasura as the base layer and used schema stitching to do our authentication since it is really complicated. I love this project. Thank you guys for support it!
POC for a internal ticketing app. Hasura + React + Ant Design. :)
I'd finished writing REST API backend few days ago for my new project. Now i can't close my local Hasura Console tab (even at night). I need only 2-3 feature and i always use Hasura (already love, but with these would be great and can use without any limits) for my all future/current projects :)
Not yet. Developing with AWS Amplify JS - AppSync on top of DynamoDB. But I don't like it at all.
DynamoDB is unworkable Spend 10 hours debugging why I didn't get my filtered results and discovered that DynamoDB scan operation is limited to 1MB! Don't go the noSQL route.
So now I'm halfway sucked in there eco-system looking to move to a Hasura - AWS cognito combination
I'm developing new products with a client for an IoT platform here in Australia. Hasura has revolutionsed how we develop API based products and real time apps. It's simply amazing. We will tell you more about the specific projects closer to go-live in a few weeks, but we're working with an awesome client called AxisTech, and together we have even open sourced tools to help the Hasura community - see https://www.npmjs.com/package/hasura-auto-tracker
Using Hasura at GMETRI. It's a platform for building AR/VR experiences on the web. It has been a few months since we started using hasura here and I can say this with absolute confidence that hasura graphql has secured a place in our current and all future workflows.
I create open source e-government platform for open data in Ukraine And back and SaaS platform city portal
@Pomazan-Bogdan Intresting. Can you share any git URL?
@shahidhk Yep we are using GraphQL at https://www.getproperly.com/en
@mnlbox Start here https://github.com/OpenData835/urp
Using in our org. We have 2 front-end products (education). And 1 hasura back-end.
We had some tricky logic to implement with views on sql (recursion + aggregation) but we made it and it's pretty awesome.
Another interesting insight we had is (as the schema grew) the need to keep a "lower" layer of very normalized tables and a "higher" layer of easy to understand and query api with views.
We even had to use materialized views for the more complex logic to keep performance reasonable.
In our company we started a new development, we are incorporating it in the backEnd.
I use Hasura to let other people accelerate at using Hasura at https://nhost.io
nhost.io is a managed service for Hasura with Auth and Storage included.
We're migrating from Prisma => Graphql Engine for some use cases that prisma was not handling.
@Disturbing Would you share some of your experience on the "use case"?
I mentioned it further down in the thread.
Prisma's horizontal scalability is there but very alpha and dependent on Rabbitmq, etc. And If you update the postgres/mysql/mongodb databse from a 3rd party source (such as infrastructure events or fluentd, etc), subscriptions/updates will not work with Prisma. For prisma clients to get updates from those rows that update directly in the DB, you must submit the update via prisma.
Hasura uses events from postgres so it scales much more nicely that way and covers the use case that Prisma wasn't. Of course we can change fluentd/infra to submit graphql updates directly to prisma vs Postgres directly for example, but it began becoming a huge mess
On Mon, Aug 12, 2019 at 10:13 PM jjangga0214 notifications@github.com wrote:
We're migrating from Prisma => Graphql Engine for some use cases that prisma was not handling. @Disturbing https://github.com/Disturbing Would you tell me what was the use case?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/hasura/graphql-engine/issues/1883?email_source=notifications&email_token=AASB5P362VFB3P5Q5GWL5XLQEFVZ3A5CNFSM4HBV7XW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4CVCPQ#issuecomment-520442174, or mute the thread https://github.com/notifications/unsubscribe-auth/AASB5P5E7PN6I3LUC7OYVRDQEFVZ3ANCNFSM4HBV7XWQ .
Hello there, We are building online book library and using the hasura for backend. from Mongolia.
Hello folks, please comment here if you or your org is using GraphQL Engine.