ReOrc docs
Get ReOrc
English
English
  • About ReOrc
  • Set up and deployment
    • Set up organization
    • Install ReOrc agent
  • Getting started
    • 1. Set up a connection
      • BigQuery setup
    • 2. Create a project
    • 3. Create data models
    • 4. Build models in console
    • 5. Set up a pipeline
  • Connections
    • Destinations
      • Google Service Account
    • Integrations
      • Slack
  • Data modeling
    • Overview
    • Sources
    • Models
      • Model schema
      • Model configurations
    • Jinja templating
      • Variables
      • Macros
    • Materialization
    • Data lineage
    • Data tests
      • Built-in generic tests
      • Custom generic tests
      • Singular tests
  • Semantic modeling
    • Overview
    • Data Modelling vs Semantic Layer
    • Cube
      • Custom Dimension
      • Custom Measure
        • Aggregation Function
        • SQL functions and operators
        • Calculating Period-over-Period Changes
      • Relationship
    • View
      • Primary Dimension
      • Add Shared Fields
    • Shared Fields
    • Integration
      • Guandata Integration
      • Looker Studio
  • Pipeline
    • Overview
    • Modeling pipeline
    • Advanced pipeline
    • Job
  • Health tracking
    • Pipeline health
    • Data quality
  • Data governance
    • Data protection
  • Asset management
    • Console
    • Metadata
    • Version history
    • Packages and dependencies
  • DATA SERVICE
    • Overview
    • Create & edit Data Service
    • Data preview & download
    • Data sharing API
    • Access control
  • AI-powered
    • Rein AI Copilot
  • Settings
    • Organization settings
    • Project settings
    • Profile settings
    • Roles and permissions
  • Platform Specific
    • Doris/SelectDB
Powered by GitBook
On this page

Set up and deployment

PreviousAbout ReOrcNextSet up organization

Last updated 15 days ago

This section provides the information and guidelines on setting up ReOrc.

Architecture overview

Recurve services are structured into two parts:

  • Control Plane: Runs within the Recurve cloud system and provides the web interface for users to manage projects and pipelines.

  • Data Plane: Receives instructions from Control Plane and runs the actual data jobs, which include data ingestion, transformation, pipeline tasks, or delivery to other systems. The Data Plane consists of multiple worker hosts that are orchestrated by the Control Plane.

This separation offers flexibility in deployment, where worker hosts of Data Plane can be installed in different locations to fit your organization's requirements in performance, maintainability, security, and compliance.

The current version of Recurve supports setting up Data Plane services within users' infrastructure.

Follow these two guides to set up your organization and install Recurve agent (the core Data Plane service):

Set up organization
Install Recurve agent