typetta VS kysely

Have you ever tried Typetta? It's a Typescript ORM based on GraphQL model definition. ;-)

Have you ever heard of Typetta? We proudly built a Typescript ORM for both SQL and noSQL databases that gives you the ability to build a completely auto-generated GraphQL server to access your data in less than 5 minutes.

Give a try to Typetta!

The GitHub repository is the following: https://github.com/twinlogix/typetta The documentation: https://twinlogix.github.io/typetta/

I think you can't implement every security policy for every type you can request in every resolver. It requires a lot of code duplication and increase complexity. It's simply not maintainable. I ended up thinking that security policies should be applied by the layer that is in charge to load the graph, but this is just my opinion. I discussed all this things in a Medium article (https://blog.devgenius.io/how-to-secure-your-graphql-api-part-1-eb41f66ec07e) where I also proposed a solution based on a library that me and my team built to simplify the data access in a GraphQL context (it's name is Typetta and you can find more details here https://twinlogix.github.io/typetta/).

I used Mongoose in the past, but I found it rough in terms of typing, that is important in a TS context. I also tried the official driver but, you know, it's only a driver. I (and my team) ended up building something new, a sort of a type-safe open-source ORM we named Typetta (https://twinlogix.github.io/typetta/). We are using it in some production projects, with a very good feedback, but my questions is still there: how do others face the problem of managing a data layer on top of MongoDB?

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