As a fallow up to the last weeks article: Spring Boot: RxJava there is one additional project:
https://github.com/jmnarloch/rxjava-scheduler-spring-boot-starter
Setup as with most Spring Boot starters is fairy simple you just drop the dependency to your project classpath and you are all set:
<dependency> <groupId>io.jmnarloch</groupId> <artifactId>rxjava-scheduler-spring-boot-starter</artifactId> <version>1.0.0</version> </dependency>
The library brings one functionality, it allows to specify the Scheduler on the RxJava reactive types: rx.Observable and rx.Single in Spring’s declarative manner – through annotations.
The basic use case is to annotate your bean methods with either @SubscribeOnBean or @SubscribeOn annotations.
Example:
@Service public class InvoiceService { @SubscribeOnBean("executorScheduler") public Observable<Invoice> getUnprocessedInvoices() { return Observable.just( ... ); } }
The motivation here is to ease the integration with Spring Framework and be able to define within the DI container the application level scheduler. Why you want to do that? There are a couple of use cases.
For example you might need to provide a custom scheduler that can be aware of ThreadLocal variables, a typical use case is to pass logging MDC context, so that afterwords the thread running within the RxJava Scheduler can access the same context as the thread that triggered the task, but the applications go beyond that.
Other typical example is for instance customize your scheduler, not relaying on the build in. In order to for instance to limit the thread pool size, considering that the build in schedulers like IO scheduler are unbounded.
In case you want to simply relay on the RxJava predefined schedulers you can still use them with @SubscribeOn annotation.
@Service public class InvoiceService { @SubscribeOn(Scheduler.IO) public Observable<Invoice> getInvoices() { return Observable.just( ... ); } }
3 comments