LakeQL
Introduction
  • Overview
  • Why LakeQL
  • Key Concepts
Getting Started
  • Prerequisites
  • Quickstart
  • Environment
  • First Run
Architecture
  • System Overview
  • Data Flow
  • Request Lifecycle
Configuration
  • Config File
  • Runtime Lifecycle
  • Environment Variables
create-app
  • Usage
  • Template Structure
  • Post-Creation
Guides
  • Custom Resolvers
  • Extending the Schema
  • Mutations
  • Set Up a Trino Mutation
  • Deploying
Endpoints
  • Definition Format
  • Field Types
  • Nested Fields
  • Mutations
  • Glossary
Contributing
  • Local Development
  • Contribution Guide
  • Architecture
GitHub
LakeQL
  1. LakeQL
  2. Architecture

Architecture

How LakeQL is layered, how data flows, and the lifecycle of a request.

LakeQL is layered so the core never depends on a specific query engine. This section covers the system overview, how data flows from a GraphQL query to SQL and back, and the lifecycle of a single request.

System Overview

The layers of LakeQL and what each is responsible for.

Data Flow

How a GraphQL query becomes SQL and a typed response.

Request Lifecycle

The lifecycle of a single request, from token to response.

Previous page

First Run

Next page

System Overview