Titan Modules

The Titan ecosystem has three module tiers, each rendered with a origin badge so you can tell at a glance where a module comes from and what its guarantees are.

Every module page in this section starts with a <span class="module-badge"></span> chip that reflects its tier.

Want a bird's-eye view of how the 16 modules interlock — who depends on whom, which combinations form common stacks, when to prefer one over a similar one? Read the Module map.

Built-in modules

built-in · @omnitron-dev/titan · /module/*

Config and Logger ship inside @omnitron-dev/titan and are auto-loaded unless you pass disableCoreModules: true. RLS guards are imported explicitly. No extra Titan package is needed for these entry points.

Official modules (titan-* packages)

official · @omnitron-dev/titan-*

Fourteen independent packages in the omnitron-dev monorepo. Each is versioned separately; adopting one does not pin you to others.

Community modules

community · @your-scope/titan-*

No third-party modules registered yet. See Community Modules for what counts, how to adopt safely, and how to publish your own.

Composition

Modules compose through the standard imports chain — order does not matter, the container resolves the dependency graph:

@Module({
  imports: [
    // Built-in (auto-loaded; shown explicitly here for illustration)
    ConfigModule.forRoot({ schema: AppConfigSchema, sources: [/* … */] }),
    LoggerModule.forRoot({ level: 'info' }),

    // Official
    TitanRedisModule.forRoot({ config: { url: env.REDIS_URL } }),
    TitanAuthModule.forRoot({ jwtSecret: env.JWT_SECRET }),
    TitanCacheModule.forRoot({ multiTier: true, l2: { client: redisClient, ttl: 60 } }),
    TitanDatabaseModule.forRoot({ connection: { dialect: 'postgres', connection: env.DATABASE_URL } }),
    SchedulerModule.forRoot({ persistence: { provider: redisPersistenceProvider } }),
    TitanMetricsModule.forRoot({ storage: { type: 'memory' } }),
  ],
  providers: [/* your services */],
})
export class AppModule {}

Redis dependency among official modules

Five official modules depend on a Redis client provided by TitanRedisModule:

• titan-cache (when L2 tier enabled)

• titan-lock

• titan-discovery

• titan-ratelimit (when storageType: 'redis')

• titan-notifications (rate limiter, preference store, rotif messaging)

Register TitanRedisModule.forRoot(...) first; the rest pick up the shared client automatically.

Choosing modules

Most backends start with a small set:

• Web API service: built-in config + logger; auth + database + cache + health + metrics.

• Worker service: built-in config + logger; database + lock + scheduler + metrics + health.

• Notification gateway: built-in config + logger; notifications + ratelimit + metrics.

• Multi-instance app: add discovery to the above.

→ Start with ConfigModule for built-in config or jump to TitanAuthModule for the most-used official module.

→ Want to build your own? Read Authoring a module — the step-by-step recipe every official titan-* package follows.