5. API Layer Problems• Many Schemas, Tables, Clusters -> one API
➡ 40 blockchains
➡ 20 schemes
➡ 100 base tables + aggregates
• One API -> many clients, diversified requirements
➡ Easy to use HTTP / RPC / REST API
➡ Different requirements to fields / data joins
➡ SaaS model
• One API -> Many demands
➡ Flexible Data Parsing
➡ Optimisation / Aggregates
➡ Dictionaries
bitquery.io
Do not make me think!
6. Approaches That We Used / Considered
• SQL ( Superset, Redash )
• HTTP JSON API
• XMLA / MDX
• GraphQL
EASY TO USE
FLEXIBILITY / FEATURES
OUR DREAM
7. Graph QL Features
• It is JSON query language
• Schema defines «What you can query»
• You query only «What you need»
• Also Supports updates and subscriptions
• AFAIK, not used for OLAP ;)
bitquery.io
14. Graph QL for Analytics
• Easy to use toolset to build analytic queries
• Off-the-shelve tools for GraphQL editing, schema
composition, observablehq, Postman, etc..
• Basis for server-less analytical applications
• API - ready solution for SaaS clients
bitquery.io
15. Projects and Plans
• Build a community
• «FlexiGraph»: Schema = func ( Schema,… )
• Complexity Estimator
• Resources Measurement
• GraphQL IDE and Dashboard Builder
bitquery.io