user5844: So I have been trying to do some fun things with Daedalus, and realised I should be able to query the node from it. This makes me wonder how to set up a limited database / querying system for my own needs out of Daedalus? Kinda like a smaller blockfrost.

user252: The node by itself is stripped down of resources to keep active records of history, so the expectation that you could query node from Daedalus to have similar capability as cardano-db-sync (which maintains kinda everything from chain, as well as from ledger events, alongwith historical view). Thus, the resource requirements from dbsync are expected to be much more.
DB Sync v13 will allow you to stop querying ledger-state data which will shave off ~8-10GB (at the expense of not saving off-chain calcs coming from ledger-state). Instead if you're after creating small-scoped utility while not being able to spend much resources, you can look at projects below:

Ogmios / Kupo
Oura / Scrolls

Of course - the more you want to store and manage historically, higher the resources required will be

5844: <p>So I have been trying to do some fun things with Daedalus, and realised I should be able to query the node from it. This makes me wonder how to set up a limited database / querying system for my own needs out of Daedalus? Kinda like a smaller blockfrost.</p>
 252: <p>The node by itself is stripped down of resources to keep active records of history, so the expectation that you could query node from Daedalus to have similar capability as cardano-db-sync (which maintains kinda everything from chain, as well as from ledger events, alongwith historical view). Thus, the resource requirements from dbsync are expected to be much more.</p>
<p>DB Sync v13 will allow you to stop querying ledger-state data which will shave off ~8-10GB (at the expense of not saving off-chain calcs coming from ledger-state). Instead if you're after creating small-scoped utility while not being able to spend much resources, you can look at projects below:</p>
<ol>
<li><a href="https://ogmios.dev" rel="nofollow noreferrer">Ogmios</a> / <a href="https://github.com/CardanoSolutions/kupo" rel="nofollow noreferrer">Kupo</a></li>
<li><a href="https://github.com/txpipe/oura" rel="nofollow noreferrer">Oura</a> / <a href="https://github.com/txpipe/scrolls" rel="nofollow noreferrer">Scrolls</a></li>
</ol>
<p>Of course - the more you want to store and manage historically, higher the resources required will be</p>
