# Squid pour Duniter, épisode 2

**URL:** https://forum.duniter.org/t/squid-pour-duniter-episode-2/11713
**Category:** Indexers
**Tags:** subsquid
**Created:** [9 January 2024 23:00 UTC](https://forum.duniter.org/t/squid-pour-duniter-episode-2/11713 "2024-01-09T23:00:00Z")
**Posts on this page:** 1
**Showing post:** 25

<div class="post-metadata">

### Author: ![poka](https://forum.duniter.org/user_avatar/forum.duniter.org/poka/32/6827_2.png) [@poka](https://forum.duniter.org/u/poka)
#### Post date: [14 January 2024 01:19 UTC](https://forum.duniter.org/t/squid-pour-duniter-episode-2/11713/25 "2024-01-14T01:19:33Z")

</div>

> [@poka](#):
>
> `@dzlzv` on Telegram

Je discute avec lui sur Telegram du coup.

Hormis le fait qu’il essai de me vendre leur solution payante de cloud [ArrowSquid](https://docs.google.com/forms/d/11rVeaax3nZWtHSSx48F25ql4solosJFmtPmTvNImOeA/viewform?edit_requested=true), voici une partie de ses réponses qui semblent confirmer les propos de @vit . Il semble aussi dire qu’on peut tout à fait remplacer le serveur graphql de squid qui est optionnel, par hasura.

> The ArrowSquid solution is a decentralized data lake, where the whole historical data is compressed and distributed across a swarm of workers. This is what makes the indexing part so fast, as you don’t ingest this data from the RPC but rather from a data lake
> 
> As it only can be deployed to a decentralized network, there’s no option to self-host this part
> 
> Yet, you can use the ArrowSquid sdk using only the RPC, but it’s slow
> 
> the sdk is open-sourced
> 
> in this repo this seems to be exactly the case — RPC-only setup, which indeed you can fully self-host without integrating to the data lake (which would enable the archive: endpoint)
> 
> as **for the FTS queries — yes, you can certainly do that, either by using the built-in PG capabilities or additionally pushing the data to ElasticSearch or smth else from your processor**
> 
> **you can also ditch our built-in graphql server and go for hasura if you want, it’s 100% optional**

> > Moi:  
> > Sound squid is quite flexible. thank you for this confirmation.  
> > I don’t understand why arrowsquid swarm should offer faster solution than simple RPC setup. Do you have a technical documentation about the way ArrowSquid works ?

> the data lake enables batch-queries, so you extract tens of thousands of events from hundreds of blocks in a single call, then batch-transform it. So it normally takes just a couple of minutes vs hours/days from the rpc
> 
> this is API it exposes: [https://docs.subsquid.io/archives/substrate/](https://docs.subsquid.io/archives/substrate/)
> 
> the rpc essentially goes through each and every block so the longer is the chain the more requests you’d need to backfill

> > Moi:  
> > thank you for this informations, we will discuss about all of this 🙂  
> > I think we will try to replace you graphql server by Hasura, but that mean we need to dig how squid is build.
> 
> why? **you can just spin it on top of the db, and you have full control over the schema (it’s in the migrations folder)**
> 
> so **integrating hasura should be very straightforward**
> 
> > Moi:  
> > In fact I didn’t work on this part yet, just my friends, so yes maybe it’s just simple
> 
> **let me know if you need any help!**
> 
> > Moi:  
> > thank you 🙂

---

_[View the full topic](https://forum.duniter.org/t/squid-pour-duniter-episode-2/11713)._