-
Notifications
You must be signed in to change notification settings - Fork 320
RudderStack's Architecture
Amey Varangaonkar edited this page Mar 31, 2021
·
1 revision
RudderStack has two major components, namely:
-
Control Plane: The control plane allows you to manage the configuration of your sources and destinations. There are two options for setting up the connections:
- Managed Control Plane: This is the easiest way to manage your source and destination configurations.
- RudderStack Config Generator: RudderStack also allows you to manage your source and destination configurations without having to sign up and use our hosted services. Please note that you cannot create transformations or Live Debugger with the RudderStack Config Generator.
-
Data Plane: This is the core engine that is responsible for:
- Receiving and buffering the event data
- Transforming the event data into the required destination format, and
- Relaying it to the destination
For a detailed understanding of the RudderStack architecture, please check our documentation.
A high-level view of RudderStack's architecture is as shown:
To know more about RudderStack, you can contact us or start a conversation in our Slack community. To see RudderStack in action, make sure you request a demo today!