Earlier Versions: Deployment or Replica Sets

In LE 6.1.0

The deployment architecture for v6.1.0 is as follows:

In LE 6.0.0

The deployment architecture for v6.0.0 is as follows:

Traffic Manager

The traffic manager consists of two containers (workloads) - The Java proxy and the Fluent Bit Sidecar. The traffic manager handles all API traffic and OAuth traffic.

All application logs are routed to a Fluent Bit Sidecar. Refer to Fluent Bit documentation for more information.

All traffic data such as Access logs, Verbose logs, and Payload logs are routed to the Fluent Bit Sidecar. The Fluent Bit Sidecar by default logs to the console. You must configure a Fluent Bit Sidecar to send logs to the external destinations such as Elastic Stack, OpenSearch.

Platform API

The Platform API provides a secure way to invoke data APIs (that is used by the Config UI) to create Local Edition database objects. All application logs are routed to the Fluent Bit Sidecar.

Loader (CacheLoader in v6.0.0; Loader from v6.1.0+)

The loader keeps the cache updated at scheduled intervals. It can update the cache for delta changes or do a full reload.

In tethered mode (introduced in v6.1.0), the loader can also sync data (configuration and policies) from Boomi Cloud API Management.

In v6.0.0	In v6.1.0+

Config UI

The Config UI provides a user interface to interact with Local Edition objects such as Services, Packages, Plans, Package Keys.