I’m actually very surprised this happened at Walmart.
I worked on an adjacent project with one of their teams many years ago. I was very surprised by how zero tolerance their policies were about receiving anything.
It may have been the team I was working with, but I remember none of them allowed us to buy them coffee from the shop in our lobby when they visited.
If you're using these for purely inference (which is what the 5000 seems like it's tuned for) the vram's the real bottleneck so you get a similar bang for your buck using last gen's cards vs. the bleeding edge.
I've also found the crypto crash has dumped a bunch of these well-worn cards on the market you can pick up a bit cheaper.
As a Canadian, I find the whole saga of how our government works with the technology sector bat-shit crazy.
All of the media's coverage up here is disingenuously about tech overreach and not about how their lobbyists tried to double-dip on revenue (both demanding an estimated $329M/year[1] from tech companies, while also receiving the ad revenue from ++1.9B pageviews[2]).
The problem is there'll probably be some kind of settlement between the government, news companies, and tech. But while this drags on, the larger oligopoly of news outlets will come out alive, while smaller news outlets are really going to suffer financially.
If you want to read more about our government's recent brain-dead policies on technology you can look up:
C-11: A streaming services bill that mandates Canadian content on foreign streamers. Not horrible, but also a great way to have "This service is not available in your region." notices in your country.
DST: A "just because" global digital services tax of 3%, which will definitely be passed onto consumers, if not lead to service blockages in Canada.
C-18: ↑ This bill. Pretty much a shakedown by the government and media companies.
> This is coming from a registered liberal party member, who's socially liberal and is consistently confronted with the thought that I may actually be conservative.
Disclaimer - I work on Hasura, so I won't comment too much on which is better.
They're all similar flavors of producing realtime results - which take similar, but different, methods to their approach.
My understanding (please feel free to correct me if I'm wrong):
- Supabase Realtime uses WAL.
- Hasura Streaming Subscriptions uses a query which will be append-only (could be a sort-by or also WAL).
- Hasura Live Queries uses interval polling, refetching, and multiplexing.
- Supabase uses Postgres RLS for authorization, while Hasura uses an internal RLS system which composes queries (which allows for features like the multiplexing above).
- All 3 use websockets for their client communication.
Really like the idea - think there's a super decent market for this kind of solution.
Only thing I'd be aware about though is making sure you're on the right side of licensing for all the vendors you're using (/ possibly who you've talked with to make sure the usage is ok).
Off the top I saw N8N on the homepage who are a little more strict about their licensing for cloud vendors. There's also Airbyte and Redpanda who use Elastic and BSL licenses to try and deter cloud vendors from packaging some parts of their services.
Hasura (https://hasura.io) | Haskell / React | Global / Remote First | Multiple Roles | Full-time
Hasura is creating tools which help developers quickly and efficiently stand-up GraphQL APIs. We provide instant-on GraphQL APIs, while providing easy-to-use resources for setting up authentication, authorization, and data-access permissions.
While general best practice is that you version your changes in git and deploy migrations with something like FlyWay I've also run into the problem of needing some form of 'audit log' to make sure no DDL changes are being made in prod (and if they are, moving them over into version control).
I have a migration which is something like this one: https://www.alibabacloud.com/help/doc-detail/169290.html which uses a trigger on `ddl_command_end` in PG to copy over the query which made the DDL change from `pg_stat_activity` to a new audit schema to stash. Can definitely help with maintenance and finding out what happened when.
The self-hosted community version has full access to JWT and webhook validation.
The SSO listed is a feature to integrate with the Hasura Cloud Dashboard for logging in and managing projects. Think Okta => Hasura Cloud => Hasura Project (Instance). We'll definitely take a look at wording it to make it more clear.
Loved that you mentioned PL/pgSQL - consistently impressed by the amount of logic that can be implemented in database using that or plv8 or its cousins. I personally have feels about why that may be a good solution for a lot of small-to-mid-to-large size build outs.
But yeah, in terms of logic we definitely expect you're going to need at least one other service for auth in the stack (for simplicity that service could also be used for any logic-based work as well).
One of the things we pride ourselves on is being non-opinionated about the logic side of the stack and trying to create as many 'escape-hatches' as possible.
Want to use db eventing? - We can event out to an external service.
Setup a custom action? - We can toss those arguments out to an external service and return a response.
Want to do some magic™ using other GraphQL tooling like Prima or Graphene? You can mesh those in with remote schemas.
We really want to build a tool that helps onboard you into the GraphQL ecosystem, but then scales with you as your stack becomes more complicated.
+1 that's probably my favorite way of doing it - https://github.com/martin-hasura/blog-django-graphql-hasura Even Django REST Framework and Hasura works pretty well cause you get auth + then if you want to do functions you get that for 'free' as well
Caching isn't discouraged or disabled in any way in the community edition of Hasura.
In terms of query-plan caching - which provides a lot of benefits for speeding up pre-query execution - that's already enabled by default as part of the Hasura engine.
Response caching is a little more complicated and requires a separate service outside of the main GraphQL server to keep the solution generalized (ex. redis, memcached, lots of other options).
We're definitely looking at ways to have some more examples as to how someone could go about rolling their own caching solution for self-hosted instances.
In the case of hosted solutions to caching, there's Hasura Cloud which pairs the cache with monitoring and some other usability and security niceties - but you could also use a service like GraphCDN (there are a couple other as well) in front of your Hasura instance which helps setup response caching.
I worked on an adjacent project with one of their teams many years ago. I was very surprised by how zero tolerance their policies were about receiving anything.
It may have been the team I was working with, but I remember none of them allowed us to buy them coffee from the shop in our lobby when they visited.