rxjava-migration

Migrate RxJava code to Kotlin coroutines and Flow incrementally by starting with simple leaf node components. Convert basic call sites to suspend functions or asFlow, validate their behavior, and expand migration layer by layer to reduce transition risk.

An incremental migration strategy isolates risk by converting simple RxJava call sites first. It uses type and operator mappings, defers complex patterns, and applies interop bridging at architectural boundaries until a full migration plan is agreed upon.

RxJava schedulers translate directly to Kotlin coroutine dispatchers during the migration process. The Skill provides specific mappings to ensure thread management and execution contexts are preserved when converting reactive streams to structured concurrency.

You can keep existing RxJava architecture during a partial migration using interop patterns. Keep-at-layer bridging connects un-migrated RxJava components with new coroutine flows, minimizing risk and allowing gradual transition across architectural layers.

Common pitfalls when converting RxJava to Kotlin Flow include mishandling complex reactive patterns and improper scheduler to dispatcher translation. The Skill prompts validation steps and rollback considerations to manage these risks during migration.

You should defer migrating complex RxJava patterns to coroutines until a comprehensive migration plan is agreed upon. Start with simple leaf node conversions to establish validation steps and rollback considerations before tackling high-risk components.