react-native-vision-camera VS Apache AGE

Take a look at https://github.com/cuvent/react-native-vision-camera

VisionCamera: A library that provides access to the platform- native camera APIs from JavaScript and even includes a engine/system to run frame processing (AI, AR, ...) straight from JavaScript by spawning a secondary JavaScript runtime with synchronous access to native functions.

yes it is. It's fully open source (github), and you can find the frame processor documentation here

As always, images make it more appealing to look at. I'm always using images with shadows and frames around them, (see this repo) but not sure if this will work for a database. If there is a really important core feature you could quickly highlight this in an "Overview" section with a codeblock. Other than that, try centering the header.

Link to the library's GitHub repo

My problem is, that it simply doesn't find the Interface Header, so I can't import it. Here is my PR with a little bit more description and the code.

What about the AGE extension for Postgres? https://age.apache.org/

Waiting for Postgres to release theirs.

I think they are talking about the AGE extension https://age.apache.org

It's my understanding of the "incubation" period of Apache Software Foundation projects is to determine if they're able to actually execute the ASF process, and a bunch of other "project maturity metrics" (https://community.apache.org/apache-way/apache-project-matur...) of which AGE currently has some self-certification: https://age.apache.org/?l=maturity#

I recognize that's not exactly an answer to the question you asked, but I would be surprised if someone other than a project member knows a more forward-looking one

Postgres has a graph extension: https://age.apache.org. This means you can keep all your data in PG and use both models.

PostgreSQL with graph extension, developed by a team at Apache Software Foundation as Apache AGE. Apache AGE uses Gremlin.

The big thing that graph dbs provide is transitive traversals of join relationships.

The problem with graph dbs is trying to return something that is not a graph. Like a count. Or derived information. And which graph model do you use? There’s more than one. Lots of information is very poorly modeled in graph dbs. Temporal organization, for example.

Ultimately, graphs are a way to use relations. But relations allow you much more flexibility to associate information (subject to the issue of transitive relationship traversal).

Mixed graph-relational is perfectly reasonable. Reasonable start here: [https://age.apache.org/]

their actual landing page is actually better than the Github one. It's a translation layer(s) to allow querying Postgres using openCypher

Depending on how one views "postgres", there are at least two extensions that allegedly do it: https://age.apache.org/ and the AgensGraph from which AGE derives

There's an extension to postgresql (I haven't used it, but I am familiar with node/edge tables in MSSQL) that allows you to do this: https://age.apache.org/