kysely VS supabase

Hello HN! I was recently introduced to Kysely (https://github.com/kysely-org/kysely), a type-safe Typescript SQL query builder, and instantly fell in love! I got inspired and wanted to make something similar for AWS DynamoDB.

Thus, I developed Tsynamo! Instead of calling it type-safe, I decided to go with type-friendly, because the library is still in an early stage, and is not 100% type-safe.

Under the hood, Tsynamo compiles the built queries into AWS SDK v3 commands. I feel that Tsynamo simplifies the AWS SDK API quite a lot since the developer doesn't have to mess around with condition/filter expressions or attribute names/values themselves, and as a bonus gets autocompletion for building the queries!

There's also a playground to test it out in your browser: https://try.tsynamo.dev. It might not have the most up-to-date API of the library in use yet, but you can get the library's main idea from there.

Since the project is still in its early stages, it doesn't yet have 100% support for all DynamoDB features, like querying indexes. The next steps will be increasing the support coverage and perhaps adding automatic type generation as inspired by kysely-codegen (https://github.com/RobinBlomberg/kysely-codegen).

Would love to get some feedback, thanks in advance!

How does this compare with my current favorite lite sqlite wrapper kysely? https://kysely.dev/

ORMs suck, but raw SQL embedded in your code sucks too.

This might be good time to plug my TypeScript non-ORM: https://jawj.github.io/zapatos/.

I should say I also like what I've seen of https://kysely.dev/ and https://pgtyped.dev/.

As we can see using Kysely with Nextjs is very simple, and it allows us to create queries in a simple way, create tables, create migrations, transactions, etc.

I've switched to kysely (https://kysely.dev) to just build SQL instead and it's nice to have full SQL access but still be type safe to my schema. Enjoying it so far.

Kysely looks like the thing most people would want. It's not a full ORM though - just a well-typed query builder.

https://kysely.dev/

Kysely

I didn't really give much thought as to which backend I would use. I already had 2 projects in Supabase (BOXCUT & MineWork), but also a few projects in Firebase too. I was more concerned at the time at actually building the product.

Sign up for SupaBase: Head over to SupaBase and sign up. Create a new workspace and project with your preferred names.

Setting up Supabase Create a new Supabase project, and get the connection string for the database from settings > database.

Supabase (start for free)

Built with Supabase, Astro, Unreal Speech, Stable Diffusion, Replicate, Metropolitan Museum of Art

Supabase will be used for storing article data in the database and the cover image of the article in storage. Chakra UI will be used to provide style to the elements. By using both, we can build the blog with ease.

For AutoRepurpose, I opted for Supabase as the backbone of the backend. It has reliably supported Penelope AI, which garnered over 15k users in 2022 without any issues.

Semantic search demo

1. Create a new Supabase project: Visit Supabase and create a new project.

Supabase positions itself as the "open source Firebase alternative." It was founded in 2020 and is a developer-friendly serverless database platform that supports over 20 frameworks, including popular tools like Next.js, React, Nuxt, Svelte, Flutter, and Vue.