> For the complete documentation index, see [llms.txt](https://wpen.donablock.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wpen.donablock.io/14.-donablock-technology/14-5-structure-of-api-and-other-infrastructures.md). # 14-5 Structure of API and Other Infrastructures DonaBlock team not only provides the internally refined data but also various API that handles the customer queries ranging in different level. This API will manage various crypto donation Widget services in its platform and further expand to provide SDK in the future. The ultimate goal of the development is to provide the most conveniently-used API with all functions introduced affixed. DonaBlock requires Multi-Contract and Multi-State Interface to be provided via web and mobile platform. According to the agreed smart contract, the service flow consists of the infrastructure configuration as represented below. 1. DonaBlock collects raw data to collect and process large data record streams in real time. 2. The server in charge of the data collection takes control of In-Memory caching (Redis, Memcached, etc) to perform high-capacity traffic processing. 3. The collected data are to be stored in the storage such as Cloud Storage, Cloud Bigtable or Cloud Datastore, and will be distributed to the large capacity storage such as BigQuery and Cloud Storage. 4. The personal information data will be encrypted and stored on the storage server, and will be used for PaaS's API Big Data Analysis service through the following infrastructure. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://wpen.donablock.io/14.-donablock-technology/14-5-structure-of-api-and-other-infrastructures.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.