# Queries and Storage Questions
**URL:** https://discuss.dgraph.io/t/queries-and-storage-questions/3664
**Category:** Dgraph
**Created:** [November 28, 2018, 4:51pm UTC](https://discuss.dgraph.io/t/queries-and-storage-questions/3664 "2018-11-28T16:51:19Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@Emanuel](https://discuss.dgraph.io/u/Emanuel)
#### Post date: [November 28, 2018, 4:51pm UTC](https://discuss.dgraph.io/t/queries-and-storage-questions/3664/1 "2018-11-28T16:51:19Z")
Hi,
I have been investigating Dgraph to see what it can provide, and how it is different from other systems.
After some research I have a few questions remaining:
1. Can you confirm that Dgraph allows concurrent transactional queries and that queries can be parallelized?
2. Is it true that Dgraph is geared more towards OLTP than OLAP, more interactive queries than analytics?
3. I read that you use BadgerDB (key-value store). I assume that is how you store the vertices, however, edges are in RDF format (with properties, however). So do you have a separate RDF storage next to Badger?
4. These are performance questions: Are edges stored with the vertex-data? Are the edge-properties stored with the edge data?
Thanks for your help,
Emanuel
---
### Author:  [@MichelDiz](https://discuss.dgraph.io/u/MichelDiz)
#### Post date: [November 28, 2018, 5:24pm UTC](https://discuss.dgraph.io/t/queries-and-storage-questions/3664/2 "2018-11-28T17:24:17Z")
> [@Emanuel](#):
>
> Can you confirm that Dgraph allows concurrent transactional queries and that queries can be parallelized?
All you need about this [Releasing distributed transactions in v0.9 - Dgraph Blog](https://blog.dgraph.io/post/v0.9/)
and [Concurrent ACID Transactions in Badger - Dgraph Blog](https://blog.dgraph.io/post/badger-txn/)
> [@Emanuel](#):
>
> Is it true that Dgraph is geared more towards OLTP than OLAP, more interactive queries than analytics?
Not sure about this statement.
> [@Emanuel](#):
>
> I read that you use BadgerDB (key-value store). I assume that is how you store the vertices, however, edges are in RDF format (with properties, however). So do you have a separate RDF storage next to Badger?
RDF is just a standard (We use to write), all data is recorded in BadgerDB as KV.
> [@Emanuel](#):
>
> These are performance questions: Are edges stored with the vertex-data? Are the edge-properties stored with the edge data?
hmm, not sure how they’re stored.
But if you wanna know about some perf see [Loading close to 1M edges/sec into Dgraph - Dgraph Blog](https://blog.dgraph.io/post/bulkloader/) (this is abour bulk only) and [Badger vs LMDB vs BoltDB: Benchmarking key-value databases in Go - Dgraph Blog](https://blog.dgraph.io/post/badger-lmdb-boltdb/) (this is about badger)
and there is [Get started with Dgraph](https://docs.dgraph.io/design-concepts/)
Cheers.
---
### Author:  [@dmai](https://discuss.dgraph.io/u/dmai)
#### Post date: [November 28, 2018, 7:19pm UTC](https://discuss.dgraph.io/t/queries-and-storage-questions/3664/3 "2018-11-28T19:19:12Z")
> [@Emanuel](#):
>
> 1. Is it true that Dgraph is geared more towards OLTP than OLAP, more interactive queries than analytics?
Dgraph is designed for OLTP though it can also be used for OLAP since queries can perform arbitrary depth joins across your data set.
> [@Emanuel](#):
>
> 1. I read that you use BadgerDB (key-value store). I assume that is how you store the vertices, however, edges are in RDF format (with properties, however). So do you have a separate RDF storage next to Badger?
> 2. These are performance questions: Are edges stored with the vertex-data? Are the edge-properties stored with the edge data?
Everything is stored as a posting list in Badger. The posting list structure is covered in the design concepts docs that @MichelDiz linked to earlier.