Rust - from PostgreSQL to Databricks using Diesel

Discover the synergy of Rust, Diesel ORM, and Databricks for efficient data pipelines, from PostgreSQL to Databricks integration

By

Jatin Solanki

Updated on

June 15, 2024

Decube utilizes Rust to abstract and standardize metadata gathered from various sources. We firmly believe that Rust will become an essential component of the data stack in the coming months/years.

In this tutorial, we'll explore the unlikely love triangle between Rust, Diesel ORM, and Databricks. These three technologies might seem like an odd combination, but when they come together, they can create powerful data processing pipelines. So, let's dive in!

Section 1: Setting up the project

To get started with using Rust, we need to set up a Rust project using Cargo - Rust's package manager. If you're not already familiar with Rust, don't worry - it's a modern programming language that's been designed to be both safe and performant. Rust has many similarities to C++, but with less of the headaches associated with that language.

Before we get started with creating a Rust project, make sure that Rust is installed on your machine. If it isn't already installed, you can download it from the official Rust website: https://www.rust-lang.org/tools/install. Once Rust is installed, open up your terminal and run the following commands to create a new Rust project:

Section 2: Adding dependencies

Now that we have our Rust project set up, we need to add some dependencies to it. As mentioned earlier, we'll be using Diesel ORM to interact with our database, dotenv to load environment variables, and serde for JSON serialization.

If you're not familiar with these libraries, don't worry! They're widely used and have great documentation to help you get started.

To add these dependencies to our project, open up your Cargo.toml file and add the following lines:

  • diesel: This is the main library we'll use for interacting with our database. It includes query building, schema migrations, and more. We're specifying the postgres feature here, as we'll be using PostgreSQL as our database.
  • dotenv: This library allows us to load environment variables from a .env file in our project directory. This makes it easy to keep sensitive information (like our database credentials) out of our source code.
  • serde: This library provides serialization and deserialization of Rust data structures. We're using the derive feature, which allows us to automatically generate serialization code for our User struct.
  • serde_json: This library provides serialization and deserialization of JSON data.

Now, let's move on to the fun stuff.

Section 3: Configuring the database connection

To connect to our database, we need to set the DATABASE_URL environment variable. This might sound like a daunting task, but it's actually as easy as pie. Just create a .env file in the root of your project and add the following line:


Replace username, password, and database_name with the appropriate values for your database. If you're using a different database, the connection string will be different.

Now that we've set up our environment variables, we can move on to the next step.

Section 4: Running a query with Diesel

With the database connection configured, we can now use Diesel to run a query against the database. In this example, we'll retrieve a list of users from a users table and serialize the data to JSON format.

But first, we need to define a struct that represents the data we want to retrieve. Create a new file in the src directory called models.rs, and add the following code:

This defines a User struct with id, name, and email fields. Now, we're ready to run our query:

 

This function establishes a connection to the database using the DATABASE_URL environment variable and retrieves the list of users from the users table using Diesel's query API. Finally, the data is returned as a vector of User structs.

Section 5: Processing data to Databricks

Now that we've retrieved our data, it's time to process it in Databricks. But first, we need to authenticate with the Databricks API. Don't worry if this sounds intimidating - it's as easy as pie.

Create a new file in the root of your project called databricks.rs, and add the following code:

This code sends a POST request to the Databricks API to authenticate and obtain an access token. Replace <YOUR-DATABRICKS-INSTANCE> with the URL of your Databricks instance.

Now that we're authenticated, we can create a new notebook in Databricks and upload the data as a JSON file. Here's the code to do that:

This code sends a POST request to the Databricks API to create a new notebook in the user's home directory, with the name rust-diesel-databricks. The data is uploaded as a JSON file using the content field. Replace <YOUR-USERNAME> with your Databricks username.

Section 6: Wrapping up

That's it! We've successfully used Rust with Diesel ORM to retrieve data from a database, and then processed that data in Databricks using the Databricks REST API. I hope you've enjoyed this tutorial, and that it's inspired you to explore the possibilities of Rust and Databricks further.

In conclusion, Rust, Diesel ORM, and Databricks might seem like an unlikely combination, but when they come together, they can create powerful data processing pipelines. And if you're ever feeling overwhelmed, just remember - it's as easy as pie!

That's it for this tutorial on using Rust with Diesel ORM and Databricks. It's amazing to see how these technologies can come together to create powerful data processing pipelines. If you're interested in exploring the possibilities of Rust and data governance, check out Decube, a unified platform for data observability, catalog, and governance that leverages Rust and now supports integration with Databricks. You can sign up for Decube. Thanks for reading!

What is a Data Trust Platform in financial services?
A Data Trust Platform is a unified framework that combines data observability, governance, lineage, and cataloging to ensure financial institutions have accurate, secure, and compliant data. In banking, it enables faster regulatory reporting, safer AI adoption, and new revenue opportunities from data products and APIs.
Why do AI initiatives fail in Latin American banks and fintechs?
Most AI initiatives in LATAM fail due to poor data quality, fragmented architectures, and lack of governance. When AI models are fed stale or incomplete data, predictions become inaccurate and untrustworthy. Establishing a Data Trust Strategy ensures models receive fresh, auditable, and high-quality data, significantly reducing failure rates.
What are the biggest data challenges for financial institutions in LATAM?
Key challenges include: Data silos and fragmentation across legacy and cloud systems. Stale and inconsistent data, leading to poor decision-making. Complex compliance requirements from regulators like CNBV, BCB, and SFC. Security and privacy risks in rapidly digitizing markets. AI adoption bottlenecks due to ungoverned data pipelines.
How can banks and fintechs monetize trusted data?
Once data is governed and AI-ready, institutions can: Reduce OPEX with predictive intelligence. Offer hyper-personalized products like ESG loans or SME financing. Launch data-as-a-product (DaaP) initiatives with anonymized, compliant data. Build API-driven ecosystems with partners and B2B customers.
What is data dictionary example?
A data dictionary is a centralized repository that provides detailed information about the data within an organization. It defines each data element—such as tables, columns, fields, metrics, and relationships—along with its meaning, format, source, and usage rules. Think of it as the “glossary” of your data landscape. By documenting metadata in a structured way, a data dictionary helps ensure consistency, reduces misinterpretation, and improves collaboration between business and technical teams. For example, when multiple teams use the term “customer ID”, the dictionary clarifies exactly how it is defined, where it is stored, and how it should be used. Modern platforms like Decube extend the concept of a data dictionary by connecting it directly with lineage, quality checks, and governance—so it’s not just documentation, but an active part of ensuring data trust across the enterprise.
What is an MCP Server?
An MCP Server stands for Model Context Protocol Server—a lightweight service that securely exposes tools, data, or functionality to AI systems (MCP clients) via a standardized protocol. It enables LLMs and agents to access external resources (like files, tools, or APIs) without custom integration for each one. Think of it as the “USB-C port for AI integrations.”
How does MCP architecture work?
The MCP architecture operates under a client-server model: MCP Host: The AI application (e.g., Claude Desktop or VS Code). MCP Client: Connects the host to the MCP Server. MCP Server: Exposes context or tools (e.g., file browsing, database access). These components communicate over JSON‑RPC (via stdio or HTTP), facilitating discovery, execution, and contextual handoffs.
Why does the MCP Server matter in AI workflows?
MCP simplifies access to data and tools, enabling modular, interoperable, and scalable AI systems. It eliminates repetitive, brittle integrations and accelerates tool interoperability.
How is MCP different from Retrieval-Augmented Generation (RAG)?
Unlike RAG—which retrieves documents for LLM consumption—MCP enables live, interactive tool execution and context exchange between agents and external systems. It’s more dynamic, bidirectional, and context-aware.
What is a data dictionary?
A data dictionary is a centralized repository that provides detailed information about the data within an organization. It defines each data element—such as tables, columns, fields, metrics, and relationships—along with its meaning, format, source, and usage rules. Think of it as the “glossary” of your data landscape. By documenting metadata in a structured way, a data dictionary helps ensure consistency, reduces misinterpretation, and improves collaboration between business and technical teams. For example, when multiple teams use the term “customer ID”, the dictionary clarifies exactly how it is defined, where it is stored, and how it should be used. Modern platforms like Decube extend the concept of a data dictionary by connecting it directly with lineage, quality checks, and governance—so it’s not just documentation, but an active part of ensuring data trust across the enterprise.
What is the purpose of a data dictionary?
The primary purpose of a data dictionary is to help data teams understand and use data assets effectively. It provides a centralized repository of information about the data, including its meaning, origins, usage, and format, which helps in planning, controlling, and evaluating the collection, storage, and use of data.
What are some best practices for data dictionary management?
Best practices for data dictionary management include assigning ownership of the document, involving key stakeholders in defining and documenting terms and definitions, encouraging collaboration and communication among team members, and regularly reviewing and updating the data dictionary to reflect any changes in data elements or relationships.
How does a business glossary differ from a data dictionary?
A business glossary covers business terminology and concepts for an entire organization, ensuring consistency in business terms and definitions. It is a prerequisite for data governance and should be established before building a data dictionary. While a data dictionary focuses on technical metadata and data objects, a business glossary provides a common vocabulary for discussing data.
What is the difference between a data catalog and a data dictionary?
While a data catalog focuses on indexing, inventorying, and classifying data assets across multiple sources, a data dictionary provides specific details about data elements within those assets. Data catalogs often integrate data dictionaries to provide rich context and offer features like data lineage, data observability, and collaboration.
What challenges do organizations face in implementing data governance?
Common challenges include resistance from business teams, lack of clear ownership, siloed systems, and tool fragmentation. Many organizations also struggle to balance strict governance with data democratization. The right approach involves embedding governance into workflows and using platforms that unify governance, observability, and catalog capabilities.
How does data governance impact AI and machine learning projects?
AI and ML rely on high-quality, unbiased, and compliant data. Poorly governed data leads to unreliable predictions and regulatory risks. A governance framework ensures that data feeding AI models is trustworthy, well-documented, and traceable. This increases confidence in AI outputs and makes enterprises audit-ready when regulations apply.
What is data governance and why is it important?
Data governance is the framework of policies, ownership, and controls that ensure data is accurate, secure, and compliant. It assigns accountability to data owners, enforces standards, and ensures consistency across the organization. Strong governance not only reduces compliance risks but also builds trust in data for AI and analytics initiatives.
What is the difference between a data catalog and metadata management?
A data catalog is a user-facing tool that provides a searchable inventory of data assets, enriched with business context such as ownership, lineage, and quality. It’s designed to help users easily discover, understand, and trust data across the organization. Metadata management, on the other hand, is the broader discipline of collecting, storing, and maintaining metadata (technical, business, and operational). It involves defining standards, policies, and processes for metadata to ensure consistency and governance. In short, metadata management is the foundation—it structures and governs metadata—while a data catalog is the application layer that makes this metadata accessible and actionable for business and technical users.
What features should you look for in a modern data catalog?
A strong catalog includes metadata harvesting, search and discovery, lineage visualization, business glossary integration, access controls, and collaboration features like data ratings or comments. More advanced catalogs integrate with observability platforms, enabling teams to not only find data but also understand its quality and reliability.
Why do businesses need a data catalog?
Without a catalog, employees often struggle to find the right datasets or waste time duplicating efforts. A data catalog solves this by centralizing metadata, providing business context, and improving collaboration. It enhances productivity, accelerates analytics projects, reduces compliance risks, and enables data democratization across teams.
What is a data catalog and how does it work?
A data catalog is a centralized inventory that organizes metadata about data assets, making them searchable and easy to understand. It typically extracts metadata automatically from various sources like databases, warehouses, and BI tools. Users can then discover datasets, understand their lineage, and see how they’re used across the organization.
What are the key features of a data observability platform?
Modern platforms include anomaly detection, schema and freshness monitoring, end-to-end lineage visualization, and alerting systems. Some also integrate with business glossaries, support SLA monitoring, and automate root cause analysis. Together, these features provide a holistic view of both technical data pipelines and business data quality.
How is data observability different from data monitoring?
Monitoring typically tracks system metrics (like CPU usage or uptime), whereas observability provides deep visibility into how data behaves across systems. Observability answers not only “is something wrong?” but also “why did it go wrong?” and “how does it impact downstream consumers?” This makes it a foundational practice for building AI-ready, trustworthy data systems.
What are the key pillars of Data Observability?
The five common pillars include: Freshness, Volume, Schema, Lineage, and Quality. Together, they provide a 360° view of how data flows and where issues might occur.
What is Data Observability and why is it important?
Data observability is the practice of continuously monitoring, tracking, and understanding the health of your data systems. It goes beyond simple monitoring by giving visibility into data freshness, schema changes, anomalies, and lineage. This helps organizations quickly detect and resolve issues before they impact analytics or AI models. For enterprises, data observability builds trust in data pipelines, ensuring decisions are made with reliable and accurate information.

Table of Contents

Read other blog articles

Grow with our latest insights

Sneak peek from the data world.

Thank you! Your submission has been received!
Talk to a designer

All in one place

Comprehensive and centralized solution for data governance, and observability.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
decube all in one image