UATU - Query on-chain data in natural language
PlaygroundNPM PackageAPI Dashboard
  • Problems UATU is solving
  • White Paper
    • Abstract
    • Introduction
      • Background and motivation
      • Objectives of UATU
      • Scope and limitations
    • UATU Architecture
      • Blockchain Nodes & Knowledge Database
      • UATU Services and Service-Specific Databases
      • UATU API Cluster
      • Natural Language Processing (NLP) module
      • UATU Query Language (UATU QL)
      • Data extraction and presentation
  • UATU Services
    • On-chain data services
      • Implementation details and data sources
    • Integration with third-party APIs (where applicable)
  • User Interface, API, and NPM Library
    • Playground for direct user queries
    • API for developers and organisations
    • UATU libraries
      • Installation and usage
      • Library features and functions
    • Security and access control mechanisms
  • Use Cases and Applications
    • End-user scenarios
    • Developer and organisation scenarios
  • Evaluation and Performance Metrics
  • Future Work and Enhancements
  • Conclusion
  • Appendix
    • UATU QL Syntax and Examples
    • Detailed Service Descriptions
    • API Documentation and Usage Examples
    • UATU Library Documentation and Usage Examples
  • Tokenomics
    • Distribution
    • Token Sale Rounds
    • User Metrics & Trade Data
    • Burning
    • Milestones
  • FAQs
    • AI Model & NLP
    • UATU QL
    • UATU Library
    • UATU APIs
    • UATU Services
      • Wallet
      • Ticker
  • Links & Social
    • Uatu Playground
    • UATU Dev Dashboard
    • Twitter
    • Telegram Community
    • LinkedIn
    • Discord
Powered by GitBook
On this page

Was this helpful?

  1. White Paper
  2. UATU Architecture

UATU Services and Service-Specific Databases

PreviousBlockchain Nodes & Knowledge DatabaseNextUATU API Cluster

Last updated 2 years ago

Was this helpful?

UATU offers a range of services tailored to different data analysis requirements. Each service has its own database, which is chosen based on the service's data structures and needs. Examples of these databases include Cassandra, InfluxDB, and MongoDB. These service-specific databases are horizontally scalable and have cache layers to reduce redundancy in API requests and server costs.

Each service contains multiple data points, such as assets, transactions, NFTs, and addresses for the Wallet service, or tokens, contracts, DEXes, and NFTs for the DApp service. Services access the Knowledge DB based on the user query requirements, ensuring that the right data is fetched for each query. Additionally, the services can interact with one another, providing users with a holistic view of on-chain data and enabling complex cross-service data analysis.

Page cover image