• Cloudflare introduced a new AI agent which really helpful to work with all configurations. It’s awesome!

• Cocoindex is a tool to “index” the codebase for further processing by any AI model.

• Writing code with 100% coverage unit tests is a very good experience! It's truly great. It makes me feel confident and no longer afraid that the code won’t work in production. With the AI within Trae editor, it’s just seamlessly incremental improvement in coding experience, just so good.

• Due to the fact of schema conflict between Hasura and Hashnode, I restructured and figured out that we can work with many different GraphQL servers (including codegen) in the same codebase, this is awesome.

• Hasura subscription doesn’t allow listening to multiple queries in the same subscription. So we need to manage different Hasura subscriptions, and programmatically manage the WebSocket connections.

Notification with Hasura

We have many ways to leverage the Hasura capability for real-time features, Hasura subscriptions is so powerful and easy for mental modeling, it’s just the data in the database.

I do think about this problem from the beginning of the core flow for my watch site:

• End-user inputs some data directly to the database via Hasura mutations

• Hasura event trigger call webhook to my Cloud Run service

• Cloud Run service does asynchronous processing and early return success results for Hasura to end up the webhook flow.

• The video processing may take hours, in fact, we don’t really know, and end users shouldn’t care either. End users want to know WHEN the progress is finished.

• From the above architecture, there are no responses to the client to let them know from the Hasura. In my architecture, all the clients must always communicate with Hasura, nothing else.

One idea I think about the notification is based on the status column of the video since the frontend can listen to some videos via Hasura subscriptions.

A few minutes later, I found that was not enough since end users could freely close the browser. When the app started, we lost the previous “processing” videos.

So the solution is to use another notifications table, which is straightforward also

• Hasura's permission was easy and straightforward to setup, users can only see their notifications

• The Hasura subscription now is just listen on the notifications table, regardless user closing browser behavior

So the flow now should be adding one more step into the video processing: create new record in the notification and we’re done.