Apache AGE VS age

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/

age

and echoing the result after converting to an age private key

I like that https://github.com/FiloSottile/age has small public keys.

> something fresh

It exists, it's called age..

Some random links

https://github.com/FiloSottile/age

https://www.reddit.com/r/crypto/comments/hr64hr/state_of_age...

https://github.com/FiloSottile/age/discussions/432

> (Acquiring keys, rotating keys, identifying compromised keys, and most importantly either reaches a large enough percentage of emails..

Oh nevermind, age doesn't do any of that. Indeed, it doesn't even do email https://github.com/FiloSottile/age/issues/93

Encrypted secrets thanks to SOPS and Age

I never heard of "Age" before this post. Thank you to share. If others are interested to learn more, here are two other interesting posts about Age:

https://github.com/FiloSottile/age/discussions/432

https://words.filippo.io/dispatches/age-authentication/

of all things I was able to resolve the issue via this github issue: https://github.com/FiloSottile/age/issues/370#issuecomment-1...

Why keep something secret on a public repo? Is that not an oxymoron?

Also, I’m terms of encryption something like age[0] makes it much easier to not shoot yourself in the foot.

[0] https://github.com/FiloSottile/age

Why RSA specifically? For backups, I recommend Tarsnap. But if you really don't want to pay for encrypted cloud hosting, then check out age encryption.