[02/Vitim/02]

REST API

Integrating data sources from a data governance suite

REST API

Stability and infrequent changes

REST API

Integrating Flow.BI into business processes

API first

Data Vault automation packages

REST API

Latest version of the data in the repository

Flow.BI App REST API

It integrates historical data with Flow.BI

Flow.BI App REST API

Host, Port, API Key

SQL API

They provide their own REST API

Flow.BI App REST API

To implement the primary REST interface

Flow.BI App REST API

In the web interface under API keys

False

True

True

False

True

False

False

True

True

True

True

True

False

False

True

True

False

True

True

True

SQL API = Provides read and write access to historical data, but with less stability in interface changes REST API = A standard JSON based web interface primarily used by application developers to integrate Flow.BI into their data-driven applications Flow.BI App REST API = The primary REST interface directly used by the Web user interface to implement the 'API-first' approach Multiple packages' REST APIs = They might be valuable depending on the task at hand, as they provide their own REST API

SQL API = Does not require an API key for every call REST API = Requires the use of an API key for every call Flow.BI App REST API = Requires the use of an API key for every call Multiple packages' REST APIs = Requirements may vary depending on the package

Provides read-only access to historical data = SQL API Can be queried with curl using a GET request = REST API Is a standard JSON based web interface = REST API Is the primary REST interface used by the Web user interface = Flow.BI App REST API

More stable in terms of interface changes = SQL API Less stable in terms of interface changes = REST API

Integrating with historical data = SQL API Integrating with external applications = REST API Implementing the 'API-first' approach = Flow.BI App REST API Using specific packages' functionalities = Multiple packages' REST APIs

Requires the use of an API key for every call = REST API Provides access to the latest version of the data in the repository = REST API Should be the preferred option for integrating external applications = REST API Is primarily used by application developers = Flow.BI App REST API

Read and write access to historical data = SQL API Only read access = REST API

Requires the use of a API key = REST API Does not require an API key = SQL API

Application developers = Flow.BI App REST API Users who need read and write access to historical data = SQL API Users who need to integrate external applications = REST API

Provides access to the latest version of the data in the repository = REST API Used to perform all actions on the internal repository = SQL API Used by the Web user interface to implement the 'API-first' approach = Flow.BI App REST API

The REST API is the preferred option for integrating external applications = True The REST API is more stable than the alternate SQL API = True The REST API calls typically provide only access to the latest version of the data in the repository = True Changes to the REST API are frequent and existing functionalities may be removed without proper notifications = False

The REST API provides read access to historical data in the repository = False The REST API can be used to integrate Data Vault automation packages such as Wherescape and dbt = True The REST API is the primary API to be used by application developers to integrate Flow.BI into their data-driven applications = True The REST API is used by the Flow.BI web frontend to perform all actions on the internal repository = True

REST API = More stable and used by application developers for integration SQL API = Less stable and provides both read and write access to historical data Web frontend = Uses the REST API for all actions on the internal repository Data-driven application = Can use the REST API to access enterprise metadata from Flow.BI

The REST API requires the use of an API key for every call = True The REST API provides a detailed documentation of its endpoints = Not mentioned The REST API can be queried with curl using a GET request = Not mentioned The REST API is described as a standard JSON based web interface = True

The REST API is primarily used by application developers to integrate Flow.BI into their data-driven applications = True The REST API can be used to add data sources to an instance based on information from a data governance suite = True The REST API is the primary REST interface used by the Web user interface = True The REST API is used to modify and delete records in the repository = True

The REST API is the primary API to be used by application developers who want to integrate Flow.BI into their data-driven applications = True The REST API provides not only read access, but is also used to modify and delete records in the repository = True The REST API provides access to the latest version of the data in the repository = True The REST API should not be used for integrating external applications in Flow.BI = False

The REST API is more stable than the SQL API = True The REST API calls typically provide access to the latest version of the data in the repository = True The REST API is used by the Flow.BI web frontend to perform all actions on the internal repository = True The REST API should not be the preferred option for integrating external applications such as integrations with Data Vault automation packages and data-driven applications = False

The REST API is the preferred option for integrating external applications = True The REST API is the primary API to be used by application developers who want to integrate Flow.BI into their data-driven applications = True The REST API provides not only read access, but is also used to modify and delete records in the repository = True The REST API calls typically provide only access to the latest version of the data in the repository = True

The REST API requires the use of an API key for every call = True The REST API is the primary REST interface used by the Web user interface = True The REST API is described as a standard JSON based web interface = True The REST API can be queried with curl using a GET request = Not mentioned

The REST API is more stable than the SQL API = True The REST API is the primary API to be used by application developers who want to integrate Flow.BI into their data-driven applications = True The REST API provides not only read access, but is also used to modify and delete records in the repository = True The REST API calls typically provide only access to the latest version of the data in the repository = True

The REST API in Flow.BI can be used to integrate Data Vault automation packages such as Wherescape and dbt. = True The SQL API in Flow.BI is more stable than the REST API. = False Changes to the REST API in Flow.BI are frequent and existing functionalities may be removed without proper notifications. = False The REST API in Flow.BI requires the use of an API key for every call. = True

REST API = Allows inserts / updates / deletes / modifications SQL API = Used by the Flow.BI web frontend to perform all actions on the internal repository API First = Approach followed by Flow.BI CSS API = Used for styling web pages

The REST API provides read access to historical data in the repository. = True The REST API should be the preferred option for integrating external applications in Flow.BI. = True The primary strategy followed by Flow.BI is an 'API first' strategy. = True The REST API in Flow.BI can be used to integrate with external applications. = True

API First

Access to latest data

Inserts/Updates/Deletes/Modifications

True

True

True

PUT

They are resource-oriented

To identify the resource you want to interact with

Google Maps API

The data to be sent to the API

The response status

JSON

They are easy to scale and cache

They are resource-oriented

Web API

REST APIs are easy to understand and use

REST APIs are flexible

REST APIs are easy to use for data manipulation

REST APIs are cacheable

Developing a wide variety of applications

REST APIs can be easily scaled up or down

The REST API allows for integration with external applications

The REST API in Flow.BI requires the use of an API key for every call

The SQL API is more stable than the REST API

Flow.BI follows an 'API first' strategy

True

True

True

True

True

True

True

True

True

True

True

True

True

True

True

True

True

True

True

True

POST = Create a new resource GET = Read a resource PUT = Update a resource DELETE = Delete a resource

REST API = Uses HTTP requests to create, read, update, and delete data Web API = A type of API that uses the web for communication Stateless API = Does not store any state or session information Resource-oriented API = Treats data as resources that can be manipulated

Google Maps API = A widely used API for mapping services Twitter API = Allows developers to access and interact with Twitter data Amazon Web Services (AWS) API = Allows developers to access and use AWS services Google Cloud Platform (GCP) API = Allows developers to integrate their applications with GCP

JSON = A lightweight data interchange format XML = A markup language for encoding documents HTTP = A protocol for transferring hypertext requests and responses URL = A reference to a web resource

Endpoint = A URL that identifies the resource that you want to interact with HTTP request = A message sent by the client to the server to perform a specific action HTTP response = A message sent by the server to the client in response to an HTTP request API key = A unique identifier used to authenticate API calls

Easy to scale and cache = REST API Widely used in various applications = Web API Stateless = Stateless API Resource-oriented = Resource-oriented API

Create a new resource = POST Read a resource = GET Update a resource = PUT Delete a resource = DELETE

REST API = Used for CRUD operations in various applications Web API = Used for communication between web-based systems Stateless API = Used when state or session information is not required Resource-oriented API = Used when data is treated as resources that can be manipulated

JSON = A lightweight data format that is easy for humans to read and write XML = A markup language that defines a set of rules for encoding documents HTTP = A protocol that defines how messages are formatted and transmitted URL = A reference to a web resource that specifies its location on a computer network

Endpoint = A specific URL where an API can be accessed HTTP request = A message sent by a client to request an action from a server HTTP response = A message sent by a server to respond to a client's request API key = A code that identifies the user and provides access to an API

REST APIs are easy to use = True REST APIs are scalable = True REST APIs are cacheable = True REST APIs are a valuable tool for developing web applications = True

Easy to use = REST APIs are easy to understand and use due to their resource-oriented design Scalable = REST APIs can be easily scaled up or down to meet the needs of the application Cacheable = The results of REST API requests can be cached and reused, improving performance Flexible = REST APIs can be used to develop a wide variety of applications

Resource-oriented design = Design approach that makes it easy to identify and interact with the data Scalability = Ability to easily scale up or down to meet the needs of the application Caching = Process of storing and reusing the results of API requests Flexibility = Ability to be used for a wide variety of applications

Web applications = Can use REST APIs to interact with data Mobile applications = Can use REST APIs to interact with data Enterprise systems = Can use REST APIs to interact with data Simple websites = Can use REST APIs to interact with data

Easy to use = REST APIs are designed in a way that makes them easy to understand and use Scalable = REST APIs can be easily adjusted to handle varying workloads Cacheable = Results of REST API requests can be stored and reused, reducing the need for repeated requests Flexible = REST APIs can be used for a wide range of applications

Ease of use = REST APIs are designed to be easily understood and used Scalability = REST APIs can be easily adjusted to handle changing demands Caching = REST APIs can improve performance by allowing the reuse of previously fetched data Flexibility = REST APIs can be used for various types of applications

Resource-oriented design = Design principle that structures APIs around resources Scalability = Ability to handle increased workload or changing needs Cacheability = Ability to store and reuse API responses Flexibility = Ability to adapt to different use cases

REST APIs are a powerful tool for developing web applications = True REST APIs are easy to understand and use = True REST APIs are scalable = True REST APIs are cacheable = True

Easy to use = REST APIs have a design that is easy to understand and use Scalable = REST APIs can handle changes in usage without affecting performance Cacheable = Results of REST API requests can be stored for future use Flexible = REST APIs can be used for a wide range of applications

Ease of use = REST APIs are designed to be easily understood and used Scalability = REST APIs can handle increased workload or changing needs Cacheability = REST APIs allow for the storage and reuse of responses Flexibility = REST APIs can be used in a variety of applications