sea-orm
oso
Our great sponsors
sea-orm | oso | |
---|---|---|
82 | 16 | |
6,045 | 3,361 | |
4.3% | 0.4% | |
9.5 | 7.1 | |
3 days ago | 6 days ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sea-orm
-
Rust GraphQL APIs for NodeJS Developers: Introduction
SQL with SeaORM:
-
Hyper – A fast and correct HTTP implementation for Rust
Haven't used it myself, but https://github.com/SeaQL/sea-orm seems to be popular in some communities and async
-
New Rustacean Looking For Guidance
sea-orm
-
Having a hard time finding Actix examples that work with Seaorm.
SeaORM has an Actix example in their GitHub. https://github.com/SeaQL/sea-orm/tree/master/examples/actix_example
-
A question for all those that use Python
SeaORM or the underlying SQLx query builder for SQL handling.
-
Rust tech stack
SeaORM is the most advanced ORM currently available, but a lot of people prefer to just skip ORMing and go direct to the underlying SQLx query builder.
-
rust web dev??
If you want to do backend development, give actix-web or Axum a try. If you need templating, take a look at Maud and if you want an ORM, take a look at SeaORM.
-
Any web frameworks that could compare to Symfony?
SeaORM is the most advanced option right now (though a lot of people prefer to go direct to the underlying SQLx library) but it doesn't yet match Django ORM for offering auto-generation of draft database migrations, which is one of the things I'm unwilling to regress on. (i.e. so all I need to hand-edit is stuff like "that's a rename, not a remove+add" and so on)
-
Anyone from a Typescript/React background who tried out Rust for the 1st time?
Last I checked, authentication was weak. SeaORM is probably the most mature option if you're looking for an ORM like you'd find in another ecosystem (if you're willing to explore alternative designs, try using the underlying SQLx directly).
-
Programming block?
What I really like about it (apart from being a really nicely designed language, that is very expressive, powerful, performant and one of the safest because of the strict typing/memory management), is that you can kind of focus on just programming, without all the hassles around setting up a project, thinking about building/deploying etc. as tooling is really awesome as well (rust-analyzer, cargo, crates.io etc.). Libraries are usually high-quality and innovative (which is IMHO not so true for a lot of different other languages, including the ones you mentioned). E.g. if you want to create a web-server/API you could try something like this (my current recommendation): https://github.com/tokio-rs/axum and https://github.com/launchbadge/sqlx for good integration of typed sql in Rust or if you want something higher level: https://github.com/SeaQL/sea-orm
oso
-
Who's hiring developer advocates? (October 2023)
Link to GitHub -->
-
Show HN: ILLA is an Open-source alternative to Retool
Not OP but Authentication is easy, authorization is a cross-cutting concern that often requires custom code. E.g., there are people and teams, both of which can have different kinds of access to something (read/write). Sometimes teams have sub-teams. Do the sub-teams have access to the parent teams' resources and/or vice versa? Also what kind of sharing are you going to support? Do people have to have an account to view stuff shared to them or can you just send a link? There are some efforts to make custom DSLs for describing authorization policies, to avoid cross-cutting code[1].
Computed fields require different treatment at every level of the stack. This isn't inherently hard, but it is an extra feature these low-code/no-code platforms need. Where things get difficult is inn migrations. It's common for a field that is computed at the beginning to become customizable, or for the computation to change. When that happens, what should the value be for old columns? Computed fields also often pull data from multiple other tables, which may require some combination of custom queries and database optimization.
-
Resource-based authentication
Oso and OpenFGA are two alternatives that implement Zanzibar-style authorisation.
-
Decoupling Authorization Logic from Code in NodeJS
There's Oso as well
-
Is Datalog a good language for authorization?
Well this was fun to see! I'm the CTO of Oso, where we're building Polar (the second of the links mentioned https://docs.osohq.com/).
I have a few really minor nitpicks, so will try and make up for it by adding to the discussion :)
First of all, it doesn't really make sense to talk about Datalog as a good language for authorization, because much like with Prolog there doesn't really exist a single implementation of it. OPA's language Rego is a datalog variant, and Polar started out as a Prolog variant (although it's not really recognisable as one any more).
And that's an important point because otherwise it would be pretty reasonable to decide that: logic programming is good for authorization => you should go find the most battle-tested language out there and use that. For example, there's SWI Prolog [1] and Scryer Prolog [2] as two of my favourites.
To me, the thing that is mind-blowing about logic programming, is (a) how powerful the paradigm is, and (b) how concisely you can implement a logic programming language. Take miniKanren [3] which is a full-blown logic language in a few hundred lines of code.
In my mind, the original article makes a decent case that logic programming is a good fit for authorization. And just generally I love anyone bringing attention to that :)
But to me, the reason logic programming is such a solid foundation for authorization logic is the pieces you can build on top of it. For Polar, we've added:
- Types! So you can write authorization logic over your data types and help structure your logic. We've implemented this by simply adding an additional operator into the language that can check types
-
Hey Rustaceans! Got an easy question? Ask here (52/2021)!
First time hearing about rhai, but there's a project in that space called Oso that's authored in Rust and uses a different DSL than Rego. You may or may not find it appealing.
-
Hey Rustaceans! Got an easy question? Ask here (44/2021)!
Authentication is probably the aspect of it that's the weakest. Authorization has a few nice libs, with Oso probably being the nicest, but authentication is mostly roll your own from what I've seen.
-
We Built a Cross-Platform Library with Rust
> Hopefully Oso open source their library.
https://github.com/osohq/oso seems to have the core, C FFI, and language bindings.
- How to manage multi tenant in fast-api
-
Why Authorization Is Hard
Hey, Oso engineer here. Good question.
The rust core is indeed called from the ruby library (as it is with all of our 5 other host libraries). The core itself is pretty complex (there's a whole parser/interpreter in there), so maintaining it in a bunch of languages would be a bit hectic.
There are some files inside `lib/oso/polar/ffi` that define the C bindings used by the rest of the library. Here's an example: https://github.com/osohq/oso/blob/main/languages/ruby/lib/os...
We use the ffi gem to make that work: https://github.com/ffi/ffi
What are some alternatives?
diesel - A safe, extensible ORM and Query Builder for Rust
sqlx - 🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite.
CASL - CASL is an isomorphic authorization JavaScript library which restricts what resources a given user is allowed to access
rbatis - Rust Compile Time ORM robustness,async, pure Rust Dynamic SQL
node-casbin - An authorization library that supports access control models like ACL, RBAC, ABAC in Node.js and Browser
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
django-guardian - Per object permissions for Django
django-rules - Awesome Django authorization, without the database
Ory Keto - Open Source (Go) implementation of "Zanzibar: Google's Consistent, Global Authorization System". Ships gRPC, REST APIs, newSQL, and an easy and granular permission language. Supports ACL, RBAC, and other access models.
cerbos - Cerbos is the open core, language-agnostic, scalable authorization solution that makes user permissions and authorization simple to implement and manage by writing context-aware access control policies for your application resources.
axum - Ergonomic and modular web framework built with Tokio, Tower, and Hyper
tauri - Build smaller, faster, and more secure desktop applications with a web frontend.