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

OLTP vs OLAP Graph Querying #1874

Open
jnayak1 opened this issue May 13, 2024 · 5 comments
Open

OLTP vs OLAP Graph Querying #1874

jnayak1 opened this issue May 13, 2024 · 5 comments
Labels
question Further information is requested

Comments

@jnayak1
Copy link

jnayak1 commented May 13, 2024

Searching the AGE documentation, I cannot find how the graph is structured internally. Is it structured similarly to Neo4j or something more like AWS Neptune? How is the data indexed?
The reason I ask these questions is because I'm curious as to whether AGE is applicable to OLTP or OLAP or both? AWS Neptune DB for instance is only for OLTP. Neo4j is capable of doing both.
OLTP queries for graph DBs are when you start at a node or a collection of nodes and traverse the graph.
OLAP on the other hand you are interested in answering questions where you need to scan the whole graph to find the answer.
My guess is that AGE is for OLTP queries but would like to know for sure.

@jnayak1 jnayak1 added the question Further information is requested label May 13, 2024
@HackettJP
Copy link

Well i use it as OLAP , postgres OLTP to a dataware house postgres with fact tables with apache age at the back , how you view your data defines if it is OLTP or OLAP, defination of OLTP is now OLAP later. real time or not.

@jnayak1
Copy link
Author

jnayak1 commented May 18, 2024

I guess what i am asking is, is AGE efficient for running OLAP queries?

@HackettJP
Copy link

True DB's performance all depends on the tin it sits on, I'm from an Postgres, Oracle 9iR1+, IBM-DB2, Abinitio , KDB+ background so money was not an issue. end of the day.

you will just have to test it with the size of the data set.

There is indexing you have to build into the tables with apache age so you need to read the docs, configure hardware to suite.
I'm even starting to go down the route is model it in apache age, then hard coding it into C++, once i have query correct.

@shinhanbyeol
Copy link
Contributor

I'm not a database expert, but
I think it might not be bad in oltp as we follow postgresql's transaction strategy, but I think graph database is more suited to olap than oltp.

and AGE is a schemaless structure
I thought that it might be possible to design more flexible when building a data mart or designing data like "star schema"

@MironAtHome
Copy link

I'm even starting to go down the route is model it in apache age, then hard coding it into C++, once i have query correct.

Any link to an example would be appreciated ( if possible ) :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants