# Architecture Overview DAPP Service nodes provide the API endpoint for users to request services. So for example, in the case of a LiquidHarmony oracle request, the developer would direct that transaction to the DSP API's endpoint, and not a normal nodeos RPC endpoint. A DSP must run: * [nodeos instance](https://github.com/eosio/eos) (eosio blockchain node) * [IPFS node](https://ipfs.io/) (file storage for vRAM and LiquidStorage) * PostgreSQL database to monitor service requests * Public API Endpoint to interact with services A DSP may also optionally run * [dfuse API node](https://www.dfuse.io/) provides dfuse's push guarantee and uses dfuse's web socket versus demux * go-ethereum RPC node for LiquidLink's EVM signing service {% hint style="info" %} If you prefer Kubernetes, checkout our k8s repo {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.liquidapps.io/liquidapps-documentation/dapp-service-providers/dsps/more-on-dsps-dapp-service-providers.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.