oso
airbyte
oso | airbyte | |
---|---|---|
16 | 139 | |
3,407 | 14,112 | |
1.1% | 2.8% | |
6.7 | 10.0 | |
about 2 months ago | 2 days ago | |
Rust | Python | |
Apache License 2.0 | GNU General Public License v3.0 or later |
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.
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.
[1] https://github.com/osohq/oso
-
Resource-based authentication
Oso and OpenFGA are two alternatives that implement Zanzibar-style authorisation.
- Oso - batteries-included framework for building authorization in your application.
-
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.
Thanks! PHP is a highly requested language for us and we've been rolling them out based on demand. You can vote for it if you want here https://github.com/osohq/oso/issues/791
airbyte
-
Launch HN: Bracket (YC W22) – Two-Way Sync Between Salesforce and Postgres
I'l also give a shout-out to Airbyte (https://airbyte.com/), with which I've had some limited success with integrating Salesforce to a local database. The particular pull for Airbyte is that we can self-host the open source version, rather than pay Fivetran a significant sum to do this for us.
It's an immature tool, so I don't yet know that I can claim we've spent _less_ than Fivetran on the additional engineering and ops time, but it feels like it has potential to do so once stabilized.
-
Who's hiring developer advocates? (October 2023)
Link to GitHub -->
- All the ways to capture changes in Postgres
-
Airbyte API and Terraform Provider – available in open source
When it says "available in open source", is that under the main airbyte repo's licensing [1], hence primarily licensed under the Elastic License v2 and therefore not typically considered open source by many?
Airbyte has previous of advertising their offering as open source while not really being as per the OSD[2]. This has been raised with them previously but without response [3][4]. They've also been extending their use of ELv2, recently moving many of their existing MIT licensed connectors to be ELv2 [5].
[1] https://github.com/airbytehq/airbyte/blob/master/LICENSE
-
Need help moving 16gb of mongodb data to tableau
As possible solution, I can suggest Airbyte(https://airbyte.com/). it's more performant than generic python script.
-
Connecting data sources to Xata with Airbyte and Zapier integrations
Airbyte, an open-source data integration engine that offers hundreds of connectors with data warehouses and databases, has gained popularity for its seamless integration and data syncing capabilities. Xata's integration with Airbyte offers a streamlined data ingestion process from any Airbyte input source directly into your Xata database.
- Data replication from postgresql to MSSQL
- Testing
-
Is it impossible to contribute to open source as a data engineer?
You can try and contribute some new connectors/operators for workflow managers like Airflow or Airbyte
-
airbyte VS cloudquery - a user suggested alternative
2 projects | 2 Jun 2023
What are some alternatives?
CASL - CASL is an isomorphic authorization JavaScript library which restricts what resources a given user is allowed to access
Airflow - Apache Airflow - A platform to programmatically author, schedule, and monitor workflows
node-casbin - An authorization library that supports access control models like ACL, RBAC, ABAC in Node.js and Browser
dagster - An orchestration platform for the development, production, and observation of data assets.
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
Prefect - The easiest way to build, run, and monitor data pipelines at scale.
django-guardian - Per object permissions for Django
meltano
django-rules - Awesome Django authorization, without the database
jitsu - Jitsu is an open-source Segment alternative. Fully-scriptable data ingestion engine for modern data teams. Set-up a real-time data pipeline in minutes, not days
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.
spark-rapids - Spark RAPIDS plugin - accelerate Apache Spark with GPUs