Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AGE in Production #2047

Closed
ishaan812 opened this issue Aug 16, 2024 · 3 comments
Closed

AGE in Production #2047

ishaan812 opened this issue Aug 16, 2024 · 3 comments
Labels
question Further information is requested Stale Stale issues/PRs

Comments

@ishaan812
Copy link

Hey guys, most of our setup is in AWS but on RDS, AGE is not supported yet. Wanted to hear more about how other folks are running AGE in production?

@ishaan812 ishaan812 added the question Further information is requested label Aug 16, 2024
@MironAtHome
Copy link

MironAtHome commented Aug 16, 2024

VM deployed on prem.
Postgres + Age and one more extension deployed by product development and implementation team.
Postgres is enterprise approved and supported database, regardless, on prem or on cloud.
So, we were lucky to be supported by our enterprise policy.
In theory, we did consider deployment over VM in cloud, but found on prem more attractive.
Having looked at AWS offerings a bit wider, found Neptune managed graph database service on AWS. DIdn't check Marketplace, but I am certain, it will provide for Neo4j. Plus, Microsoft SQL Server RDS managed instance should support latest features, including built - in graph database support.
In case these offerings present interest and additional information can help.
Having looked, yet, at a slightly different angle, for example, this Netflix GraphDB foray.
It would be very - very nice to see Age Graph Database supporting similar type of enterprise workloads. As it fits the purpose nicely.

Copy link

This issue is stale because it has been open 60 days with no activity. Remove "Abondoned" label or comment or this will be closed in 14 days.

@github-actions github-actions bot added the Stale Stale issues/PRs label Oct 16, 2024
Copy link

This issue was closed because it has been stalled for further 14 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested Stale Stale issues/PRs
Projects
None yet
Development

No branches or pull requests

2 participants