System, method, and computer program for configuration based coexistence routing

A computer program product embodied on a non-transitory computer readable medium, comprising computer code for:

• interfacing a migration source system;
• interfacing a migration target system;
• during a coexistence period of a data migration process where data of the migration source system is in process of being migrated to the migration target system, storing in a migration master database for each entity of a plurality of entities included in the data:
• a routing key for the entity included in the data, and
• an indication that defines whether the entity has been migrated yet to the migration target system;
• receiving a service call related to at least one entity of the plurality of entities;
• identifying one or more routing keys included with the service call;
• querying the migration master database using the one or more routing keys identified from the service call to determine whether the at least one entity related to the service call has been migrated yet to the migration target system;
• routing the service call to the migration source system when a result of the query indicates that the at least one entity related to the service call has not yet been migrated to the migration target system;
• and
• routing the service call to migration target system when a result of the query indicates that the at least one entity related to the service call has been migrated to the migration target system;
• wherein the data migration process is performed in phases, and wherein the coexistence period is a period of time between a first migration run and a last migration run.

A coexistence router system, operable for:

• interfacing a migration source system;
• interfacing a migration target system;
• during a coexistence period of a data migration process where data of the migration source system is in process of being migrated to the migration target system, storing in a migration master database for each entity of a plurality of entities included in the data:
• a routing key for the entity included in the data, and
• an indication that defines whether the entity has been migrated yet to the migration target system;
• receiving a service call related to at least one entity of the plurality of entities;
• identifying one or more routing keys included with the service call;
• querying the migration master database using the one or more routing keys identified from the service call to determine whether the at least one entity related to the service call has been migrated yet to the migration target system;
• routing the service call to the migration source system when a result of the query indicates that the at least one entity related to the service call has not yet been migrated to the migration target system;
• and
• routing the service call to migration target system when a result of the query indicates that the at least one entity related to the service call has been migrated to the migration target system;
• wherein the data migration process is performed in phases, and wherein the coexistence period is a period of time between a first migration run and a last migration run.