Nomenclature
Venice tries to be as clear and consistent as possible with the nomenclature used throughout the documentation and code base.
To that end, here’s a list of what our primitives are and examples of how you can think of them in use.
Need clarity?
Join our community
Join our community of founders & developers building the future of finance together
Improve the documentation
Help us keep the documentation as clear as possible. We welcome pull requests!
Nomenclature
Used in a sentence: A Pipeline simply connects a data Resource to/from Venice which transmits data across the Pipeline protocol, storing any data in Venice’s unified Database and making it available via an API.
| Term | Description | Example |
|---|---|---|
| Resource | A generic resource which can be used as a Source within a Pipeline (e.g. kept agnostic of how it is connected within Venice) |
|
| Pipeline | Pipeline moves data from a Source to a Destination, with Venice ultimately being the first destination we support |
|
| Integration | A specific configuration of a Provider. |
|
| Provider | Source code adhering to our protocol for reading or writing data into or out of Venice, including the schema for how data is transformed to be compatible with an external Resource |
|
| Database | The primary data store connected to Venice where all of your unified data is stored | A PostgreSQL Database configured to act as Venice’s primary data store. Database can also be a Resource and act as a Source of data. |
| API | A developer interface into Venice’s unified Database that can be called to read or write data from or to Venice |
|
When we say “connect” in the user interface, we typically mean to create a new resource and setup a pipeline either to or from the Venice Database
Data models
For terminology used within our unified database schema, please refer to the Data Models documentation.