hono VS drizzle-orm

This is a template for creating your first Copilot extension. It's a simple Node.js app that uses Hono and leverages the GitHub Copilot Extension Preview SDK for JavaScript.

Hono - means flame🔥 in Japanese.

In this example, we'll use Hono as our server framework. I chose it for two reasons:

Hono - Fast, lightweight, built on Web Standards. Support for any JavaScript runtime.

Hono has built in support for complex tools like RPC, AWS, Edge functionality, Cloudflare, JSX and many more. Obviously you can go and check out their official website at hono.dev and get better understanding of various features they offer as there are a lot!

Hono is a great framework to build serverless apps with familiar APIs using Web Standards. It comes with a ton of features out of the box.

Today we'll try to answer these questions by looking at some methods to stream real-time data and build our own small real-time stock market feed app in Hono and React to illustrate the differences between these methods. For the visual side of things we'll be using shadcn charts to display randomly generated data.

But that’s not all. The framework offers a powerful routing system (inspired by the fantastic Hono), integrated asset management with Cloudflare R2, and an elegant way to handle errors via the HttpError class. Middlewares can easily send data to the client through a shared store, and everything is automatically obfuscated for security.

Drizzle for our ORM

Drizzle ORM - you can define and manage database schemas in TypeScript, access your data in a SQL-like or relational way, and take advantage of opt-in tools to push your developer experience through the roof.

Type-safe query builders sound great in theory, but it seems there are always edge cases that are not supported by the query builder.

For example, the issue asking for deferrable constraint support for Postgres has been open for about a year: https://github.com/drizzle-team/drizzle-orm/issues/1429

In any non-trivial application, you are increasingly likely to run into something that your database supports but your query-builder does not. What will you do then?

It's sad, but unfortunately the most reliable approach seems to be to write raw SQL in a DAO package/library, then using integration tests (DAO + database) to confirm behavior.

Our Lambda function is currently using raw SQL queries which are not the most fun to write and maintain. Let's replace them with Drizzle ORM, a popular TypeScript ORM.

Drizzle: Database ORM

ORM: Drizzle

In this post, I’ll walk you through how to work with ORMs like Prisma, Drizzle and Knex.js when working with Encore.ts.

That’s why we’ve partnered with Drizzle ORM to offer a cleaner, more intuitive way of defining RLS rules. With Drizzle and Neon, developers can set up RLS policies in a declarative format right alongside their schema definitions. This means you can manage RLS in the same place as your schema and data models, making your codebase more organized and easier to maintain.

Drizzle [0] added an easter egg on their website in response to this announcement it seems.

[0]: https://orm.drizzle.team/