This article is getting a lot of hate but honestly it does have good amount of useful content learned through practical experience, although at an abstract level. For example, this section:
```
The teams that succeed don’t just throw SQL schemas at the model. They build:
Business glossaries and term mappings
Query templates with constraints
Validation layers that catch semantic errors before execution
```
Unfortunately, the mixing of fluffy tone and high level ideas is bound to be detested by hands on practitioners.
Exactly! Midnights Children and Moors Last Sigh are so non-linear that one cannot expect to get the hang of it till they are atleast 50 pages through. It's usually on the second reading that the amazingness of those initial pages is felt.
Big Rushdie fan here. I used to think it could be because of a lack of cultural context especially for books like Midnights Children and Moors Last Sigh but now I also think that it could also be a matter of taste. Rushdie himself quotes Milan Kundera who said: "...that the novel descended from two parents, Samuel Richardson’s Clarissa and Laurence Sterne’s Tristram Shandy". The latter is a style of writing where all conventional rules of literature are broken, it's just wildly creative so to speak. Rushdie's Midnights Children and James Joyce's Ulysses fall into this category.
If you want to see the other style of writing in Rushdie, I can suggest Shalimar The Clown or The Ground Beneath Her Feet. But these are nowhere near as grand as Midnights Children.
In either category, a fair amount of interest in history helps to enjoy his books.
PromptQL is a programmatic approach to LLM tool composition which has shown remarkable improvement in accuracy (~2x) and repeatability (~4x) when compared to traditional tool calling and chaining approaches.
Fundamentally, PromptQL separates the creation of a query plan from the execution of the query plan. PromptQL uses the LLM to first create a program to compose the different tool calls hence avoiding the challenges with in-context tool chaining like accuracy, repeatability and context limits.
Hasura is a venture-backed open-source and Cloud technology company that makes your data instantly accessible over a real-time GraphQL and other API technologies. Hasura connects to your databases, REST servers, GraphQL servers and third party APIs (eg: Stripe, Salesforce) and provides a unified API across all your data sources.
Hasura is looking for a Senior/Staff Software Engineer with proficiency in Rust to become part of the core engineering team. In this position, you will work on developing innovative features on the core product. We are writing the core components of the product in Rust to accelerate feature velocity hence Rust expertise is required. This is an exciting time to join this effort in the early stages.
I work at Hasura. You don't need an append-only table always. You may have to add a monotonic ID to your table which increments on DMLs (and use it as the cursor for streaming) and this can be done using a post-DML trigger in Postgres. Also, streaming works over tables with relationships as well so you can get related data in the same stream as well.
Hasura uses a novel way of batching similar parameterized subscriptions together and then polls under the hood. This means that if there are 1000 subscribers of similar type of query, then underneath Hasura will only make a single query to Postgres (or few queries depending on the batch size). This approach, which we call "multiplexing" in short, scales really really well. And is also the simplest way to get live updates for _any_ query, no matter how many joins, etc.
> That setup can be great when your application doesn’t require a lot of business logic and the CRUD capabilities that are exposed in the GraphQL API fit your needs (though I believe you can add business logic in Hasura by integrating serverless functions).
(I’m from Hasura)
You can extend business logic in Hasura in a number of ways, including (but not exclusively) ones that work well with serverless and async architectures. Other examples follow:
1. You can extend it by adding business logic in the database via user-defined functions.
Eg: You want a fulltext search or a PostGIS function that is better off in the DB anyway.
2. You can bring your own GraphQL server with custom resolvers and Hasura will merge them into its own API and let you “join” across them as well.
3. You can bring REST APIs and add graphql types for them in Hasura and use it as custom resolvers that extend the schema as well.
Hasura’s key value add is an instant GraphQL API backed by your own data-sources (database, GraphQL, REST) and then a fine-grained authorization system on it.
Like Nikolas said, very different from Prisma. Hasura aims to add value as “infrastructure” by guaranteeing performance and security where as Prisma is like an ORM/database toolkit.