Local metadata and caching

Caching metadata

Boomi Console uses a cached approach to avoid roundtrips to the (by nature slow[er]) API.

Local Metadata

Boomi Console saves all metadata responses to the file system ProjectDir\Metatdata. This data is there for you, only. It is not used for caching, but sometimes it is helpful to look-up or search in these XML files.

SQLite DB

A SQLite database in your workspace directory is used to cache persist API responses. This DB caches the Boom Component Metadata API respones by Component ID and Version.

The Component metadata is versioned (on save) and it does not change for a specific version (immutable).

Based on this "assumption" we can store/cache Component metadata under their ID plus Version. Whenever there is a request for a specific component version, a database look-up takes place. If it fails, an API request is sent and the database updated with the response.

SQLIte bc.db.sqLite

All requests which do not specify and explcit component version are directly sent to the API, because the most recent version of the component is required directly from the repository.

You can delete this file at any time, however it'll be created again when you run a command.

In-Memory cache

There is an in-memroy cache is available only during a single commands execution. It is there to buffer already read component to avoid reading the same component twice during the same run. The cache cannot be modfied or cleared.