An app allows you to extend CloudBees SDM by adding new data types and behavior such as ingesting data from third-party services. Apps can be classified into similar groups which informs the architectural and design decisions for the app. The primary dimension is the type of apps. In the Creating your first app tutorial, you will create a simple app for CloudBees SDM.
Data ingestion apps allow you to create new data types in the System of Record and to add data to the System of Record from a third-party system, such as GitHub, Jira, and Jenkins.
When designing a data ingestion app, consider the tenancy model of the third-party system:
- Single Tenant
In a single tenant system, an instance (and the supporting infrastructure) serves a single customer, including data storage. This model typically provides great isolation but has high management overheads.
- Multi Tenant
In a multi tenant system, an instance (and the supporting infrastructure) serves multiple customers, including data storage. This model typically sacrifices some isolation but provides a lower management overhead.
- Multi-single Tenant
A multi-single tenant system is a variant of multi-tenant systems, where a single system provisions and manages an instance per customer. This model provides a compromise between lower management overhead and greater isolation.
In this tutorial, you will create a data ingestion app that ingests data from a single-tenant system using a cloud-hosted system
The CloudBees SDM software developer kits (SDKs) make developing your app easier. They provide support for:
Client for interacting with app registration and installation APIs.
Optionally, a CLI for calling those commands.
An executable code sample which will call the System of Record API.
Client for interacting with the System of Record.
Client for obtaining access tokens.
SDKs are currently available for:
In the Creating an app with Go tutorial, you will create a data ingestion app that ingests data from a single-tenant system using a cloud-hosted system.