RFC: Plugins and Integrations to Serinus

[francescovallone]

Expand the Serinus Ecosystem

Serinus is an innovative solution for backend development, offering a robust, scalable, and efficient foundation for building high-performance applications. However, to truly unlock its full potential, we must expand its ecosystem of plugins.

Why Plugins Matter

Plugins are the bridge between core framework capabilities and seamless developer experience. They provide:

• Extended Functionality – Out-of-the-box solutions for common use cases (e.g., database integrations, caching, logging).

• Faster Development – Pre-built plugins reduce time spent on writing boilerplate code, allowing developers to focus on core business logic.

• Interoperability – Enabling smooth communication with third-party services and existing technologies.

Proposed Integrations

• Redis (Caching)
• Memory Cache (Caching)
• Queues
• Socket.io (WebSockets)
• Cron (Task Scheduling) -> serinus_schedule
• HttpModule (Http Client)
• Server-sent Events
• Health Checks
• ODM
• Compression Algorithms

[francescovallone]

@mjablecnik the Task Scheduling plugin will be released tomorrow :) let me then know if you encounter any issues with it.

[mjablecnik]

@francescovallone When I read documentation for serinus_schedule, it looks like schedule is setup after call of endpoint.
But I want to setup schedule automatically after start of serinus without calling any endpoints.
Is it possible?

[mjablecnik]

I have some endpoints that perform certain tasks, and I want to run them automatically every day at a specific time instead of calling them manually.

[francescovallone]

@mjablecnik thank you for your comment, next time please refer to a new issue since I would like to keep this only for requests of new integrations for Serinus.

Anyway, you can achive what you want by using Composed Providers and Lifecycle Hooks.

class YourProvider extends Provider with OnApplicationBootstrap {

  final ScheduleRegistry registry;
  
  YourProvider(this.registry);
  
  Future<void> onApplicationBootstrap() async {
	registry.addCronJob();
  }

}

class YourModule extends Module {
  
  YourModule() : super(
    imports: [ScheduleModule],
    providers: [
      Provider.deferred(
      	(ScheduleRegistry registry) async => YourProvider(registry),
        inject: [ScheduleRegistry],
        type: YourProvider
      )
    ]
  );
  
}

If one provider is available in the Controller it is because the module scope contains it. This rule is valid also for exported providers from imported modules.