Provider and Service Adapter Patterns

StratoFusion uses the word adapter for two related but distinct module families. This guide explains both and, importantly, records which path the default service registry uses today.

Read Provider Abstraction and Service Layer first for the contracts, canonical models, account boundary, and runtime flow.

Current wiring

The default server path is:

src/config/services/registration.ts
  -> src/services/ServiceRegistry.ts
  -> src/services/GoogleDriveService.ts
     src/services/OneDriveService.ts
     src/services/DropboxService.ts

The registry does not currently construct src/infra/providers/*Provider or automatically wrap every service with src/services/adapters/CloudStorageAdapter.

That distinction matters during maintenance: code existing in an adapter directory does not prove that production requests pass through it.

Provider-specific adapters under src/infra/providers

Google Drive, OneDrive, and Dropbox each have a facade that implements the narrow CloudStoragePort and delegates to focused modules:

<Provider>Provider
  -> <Provider>FileAdapter
  -> <Provider>FolderAdapter
  -> <Provider>SearchAdapter
  -> FileTransformer / ErrorTransformer

The concrete directories are:

• src/infra/providers/google-drive/;
• src/infra/providers/onedrive/; and
• src/infra/providers/dropbox/.

These facades are useful injection targets for application use cases and demonstrate the intended deep-module shape. They are not the implementation loaders used by ServiceRegistry today.

Responsibilities