Databricks Assets ?
Tags: databricks, databricksassets, datacatalog, workspaceasset
Published: 2022-09-25 12:13:01

Talking about Data Science & Engineering workspace, the classic **_Databricks_** environment for collaboration among Data Scientists, Data Engineers, and Data Analysts. Just mentioning it is the backbone of Databrick’s machine learning environment and provides an environment for accessing and managing all your Databricks assets, you might be asking yourself what sorts of assets I'm talking about? The below figure shows the some of the Data assets & all three Personas assets in Databricks.

![Databricks Assets](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/q01hffwwrmvp96xrli2y.png)

Sounds Interesting right? Let's address all of them one by one in this blog with some short description to get to know all of them.


![Data Assets in Databricks](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/u09hxvn8l3vsa6k543l0.png)


1. **_Data assets_**, while accessible from the space fall under the category of unity catalog i: e., Databricks data governance solution,

- These assets include _Databases_, _Tables_ and _Views_ also included under this umbrella or _catalogs_, which is a top-level container that contains the database
- _Storage credentials_ and _external locations_ which managed credentials and paths for accessing files and external cloud storage containers
- _Share recipients_, which are special assets in principles for use with Delta. Sharing the open-source high-performance secured data sharing protocol developed by Databricks.


![ Databricks SQL & ML Assests](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/w3n0pq8tazfn1mfh1x1p.png)

2. These assets like _Queries_, _Dashboards_, _Alerts_, and _Endpoints_ also, do not fall under the category of Data Science and Engineering workspace, but rather manage and access within Databricks SQL, likewise _Experiments_ and _Models_ are managed within Databricks Machine Learning. 

3. Data Science & Engineering workspace, the classic Databricks environment for collaboration among Data Scientists, Data Engineers, and Data Analysts. Just mention it is the backbone of Databrick’s machine learning environment and provides an environment for accessing and managing all your Databricks assets These assets are:

- **_Notebooks_**, arguably, the centerpiece of the data science and engineering workspace cost to feed a web-based interface to documents that contain a series of cells. These cells can contain commands that operate on data in any of the languages supported by Databricks. Visualizations that provide a visual interpretation of an output narrative text can be employed to document the notebook Magic commands that allow you to perform higher-level operations, such as running, other notebooks invoking, a database utility, and more notebooks that are collaborative. They have a built-in history and users can exchange notes. They can be run interactively or in batch mode as a job through Databricks workflows.


![Notebook Assets](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/wdyi5bmiint31o87ycv1.png)

- **_Folders_**provide a file system, like construct within the workspace, to organize workspace assets, such as notebooks.


![folder](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/9g680zr24fn79pvdcc0l.png)

- While notebooks provide a built-in history that can be very handy in many circumstances. The functionality is limited and does not go far to fulfill the requirements of a fully-fledged CI/CD environment. **_Repose_**provides the ability to sync notebooks and files to remote git. Repose provides functionality for Pushing and Pulling, Managing Branches, Viewing Differences & reverting changes. Repos also provide an API for integration with other CI/CD tools. 


![repose](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/gdkz6ghw0aan63vrg6zs.png)

- Databrick **_Secret_** fulfills security best practices by providing secure key-value storage, for sensitive information allowing you to easily decouple such material from your code. 


![secret](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/7kveyhhqgaffa2omfqqt.png)

- **_Jobs_** have the capability of automatically running tasks. Jobs can be simple with a single task or can be large multitask workflows with complex dependencies. Job tasks can be implemented with notebooks, jobs pipelines, or applications written in Python Scala, and Java, or using the spark summit style. 


![Jobs](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2raeb0sgskd1lo2q0k56.png)

- Delta live table is a framework that delivers, a simplified approach for building reliable, maintainable, and testable data processing **_pipelines_**. The main unit of execution in Delta live tables is a pipeline which is a directed acyclic graph, linking data sources to target datasets. pipelines are implemented using notebooks. 


![pipelines](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/tlnk1oulk8ikbrj0ab2n.png)

- A **_cluster_** is a set of computation resources and configurations on which you run Data, Engineering, Data Science, and Data Analytics workloads such as production ETL pipeline, streaming analytics, Ad-hoc analytics, and Machine Learning. The workloads can consist of a set of commands in a notebook or a workflow that runs jobs or pipelines. 


![cluster](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/lltzjherckjtqsg2i0rz.png)

- **_Pools_** reduce cluster start, and auto-scaling times by maintaining a set of idols ready-to-use virtual machine instances when a cluster is attached to a pool, cluster nodes are created using the pool idle instances, creating new ones as needed.


![pools](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/qo98agt2fxp2zdmw4a62.png)

_NOTE: Reference & Images in the blogs are taken from Databricks site & courses._

This is it for this blog, hope you like the blog. Kindly do Follow.