Controlplane vs dataplane code#

The JUNOS platform architecture separates the control and forwarding functionality in the router: You can do so by editing the config.yaml file to suit your application's needs.Architecture of the JUNOS SystemThe JUNOS SDK is designed to work with the unique modular architecture of Juniper routers. Some of these include backing up events to S3, rejecting malicious requests by defining the maximum size of the event, and more. Once the event data reaches the destination, the router deletes it from the database.Īlthough the default configuration works just fine for most use cases, RudderStack also gives you the flexibility to customize the data plane with a variety of configuration options. Stores the event information in a separate table in the database. Sends the transformed event data to the specified destinations. This event is then deleted from the gateway store. The processor forwards the transformed event to the router. The transformation module transforms the event and sends it back to the processor. The processor module picks the data from the gateway and forwards it to the transformation module.

Sends an HTTP 200 status acknowledging receipt of the data.

Stores event data in the router database (PostgreSQL).

The gateway module receives event data from the source. The following steps detail the RudderStack data plane workflow: RudderStack does not persist any events or store any user information in the database. These include but are not limited to: event enrichment, filtering, removing sensitive PII information, etc.

Controlplane vs dataplane code#

RudderStack also supports user transformations that let you code custom JavaScript functions to implement specific use-cases on your event data. All the transformation code is written in JavaScript. RudderStack's Transformations module transforms received event data into a suitable destination-specific format. Once event data is transformed, the processor forwards it to the router module that sends it to the required destination. The processor fetches data from the gateway and forwards it to the transformation module. Once event is successfully sent to the destination, it is then deleted from the database. The gateway also temporarily stores all received event data into an internal PostgreSQL database before acknowledging successful receipt. The gateway rejects event data in case of the following scenarios: Standalone streaming database (PostgreSQL) for event data.The RudderStack data plane consists of three major components: Transforming events in the required destination format.The data plane (backend) is RudderStack's core engine responsible for: Configuration backend: The web app leverages this module to store all the relevant information around your configured sources, destinations, and the connections between them.RudderStack web app: The front-end application where you set up and configure your data pipelines in RudderStack.The control plane offers a UI to configure your event data sources and destinations. RudderStack's architecture consists of 2 major components: the control plane and data plane, as seen in the following diagram: Control plane Its backend is written in Go, with a rich UI written in React.js. RudderStack is a standalone system dependent only on a database ( PostgreSQL).