# Technology Overview The following figure illustrates the technology framework of FADO Go: ![](/files/1bD2mPOdLyA3S9X4SBeH) We are currently using SaaS services from Amazon partners such as Amazon SQS, SES, S3 to help optimize costs in information management and execution of marketing activities, as well as project plans to use other technologies in the future, such as Redshift, Quicksight, Kinesis, Sagemaker, etc. Besides, Blockchain is a central technology that we want to focus on. In which, we will apply blockchain protocols and build application layers to implement our decentralized vision, i.e Wallets, Multi-chain Assets, Loyalty System, Multi-crypto Integration, Crypto Staking, and finally Cross-chain & DeFi. Next, IT infrastructure has been implemented by FADO Go, such as Private Cloud Computing, System Monitoring, Network Monitoring, especially Content Delivery Network (CDN) to help distribute content, help bring data to users the fastest, and finally, Storage, which helps the system to store all the data of FADO Go. Finally, in the Containerized Apps section, which includes technologies such as Database Management System, Web Services, and No SQL that provide a mechanism to store and retrieve modeled data, the Search Engine Service helps customers find products on demand. In addition, the Caching service is a temporary storage service. The system is faster. Similarly, the queue service helps asynchronously handle data, prioritizing important issues first. --- # 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.fadogo.io/technology/technology-overview.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.