docs(SQS): improve SQS and router documentation (backport #7031) (#7273)

* docs(SQS): improve SQS and router documentation (#7031) (cherry picked from commit 3fc43c7) # Conflicts: # ingest/sqs/README.md * Update ingest/sqs/README.md * Update ingest/sqs/README.md --------- Co-authored-by: Roman <[email protected]>
osmosis-labs · Jan 9, 2024 · ac6aa18 · ac6aa18
1 parent 6f1ee58
commit ac6aa18
Showing 1 changed file with 7 additions and 1 deletion.
diff --git a/ingest/sqs/README.md b/ingest/sqs/README.md
@@ -444,4 +444,10 @@ non-empty string, leading to the pool being deprioritized from the router.
 ## Open Questions
 
 - How to handle atomicity between ticks and pools? E.g. let's say a block is written between the time initial pools are read
-and the time the ticks are read. Now, we have data that is partially up-to-date.
+and the time the ticks are read. Now, we have data that is partially up-to-date.
+SQS is meant to offload the query load from the chain node to a separate server. Primarily, we use it for swap routing.
+
+## Integrator Guide
+
+Follow [this link](https://hackmd.io/@3DOBr1TJQ3mQAFDEO0BXgg/S1bsqPAr6) to find a guide on how to 
+integrate with the sidecar query server.