Stateful service with partial replication

A method, comprising:

• causing at least one first node to be provided with software and initialized with data, wherein the data is comprised within a message queue for duplicating in the at least first node any one of an application state or an actor state in at least one second node, but not duplicating the at least one second node's entire data, wherein the message queue comprises a master message queue and a slave message queue that are similar to each other, wherein the message queue comprises messages arriving at the at least one second node via a transaction node before the at least one second node is terminated, and wherein the messages are retained at the transaction node in the message queue in connection with forwarding the messages to the at least one second node;
• causing the at least one second node to be set to a standby mode, wherein the at least one second node in the standby mode subscribes to the master message queue, and wherein the at least one second node in the standby mode does not send any acknowledgment messages;
• causing the at least one first node to be set to a slave mode after being initialized with the data, wherein the at least one first node in the slave mode subscribes to the slave message queue, and wherein the at least one first node in the slave mode does not send any acknowledgement messages;
• causing a load balancer to be updated with information concerning the at least one first node in the slave mode;
• and
• terminating the at least one second node, and setting the at least one first node to an active mode after terminating the at least one second node, wherein the at least one second node in the active mode subscribes to the master message queue, and wherein the at least one second node in the active mode sends acknowledgment messages.

An apparatus, comprising:

• means for causing at least one first node to be provided with software and initialized with data, wherein the data is comprised within a message queue for duplicating in the at least first node any one of an application state or an actor state in at least one second node, but not duplicating the at least one second node's entire data, wherein the message queue comprises a master message queue and a slave message queue that are similar to each other, wherein the message queue comprises messages arriving at the at least one second node via a transaction node before the at least one second node is terminated, and wherein the messages are retained at the transaction node in the message queue in connection with forwarding the messages to the at least one second node;
• means for causing the at least one second node to be set to a standby mode, wherein the at least one second node in the standby mode subscribes to the master message queue, and wherein the at least one second node in the standby mode does not send any acknowledgment messages;
• means for causing the at least one first node to be set to a slave mode after being initialized with the data, wherein the at least one first node in the slave mode subscribes to the slave message queue, and wherein the at least one first node in the slave mode does not send any acknowledgement messages;
• means for causing a load balancer to be updated with information concerning the at least one first node in the slave mode;
• means for terminating the at least one second node;
• and
• means for setting the at least one first node to an active mode after terminating the at least one second node, wherein the at least one second node in the active mode subscribes to the master message queue, and wherein the at least one second node in the active mode sends acknowledgment messages.

A non-transitory computer readable medium having stored thereon a set of computer readable instructions that, when executed by at least one processor, at least:

• causes at least one first node to be provided with software and initialized with data, wherein the data is comprised within a message queue for duplicating in the at least first node any one of an application state or an actor state in at least one second node, but not duplicating the at least one second node's entire data, wherein the message queue comprises a master message queue and a slave message queue that are similar to each other, wherein the message queue comprises messages arriving at the at least one second node before the at least one second node via a transaction node is terminated, and wherein the messages in the message queue are retained at the transaction node in connection with forwarding the messages to the at least one second node;
• causes the at least one second node to be set to a standby mode, wherein the at least one second node in the standby mode subscribes to the master message queue, and wherein the at least one second node in the standby mode does not send any acknowledgment messages;
• causes the at least one first node to be set to a slave mode after being initialized with the data, wherein the at least one first node in the slave mode subscribes to the slave message queue, and wherein the at least one first node in the slave mode does not send any acknowledgement messages;
• causes a load balancer to be updated with information concerning the at least one first node in the slave mode;
• and
• terminates at least one second node, and sets the at least one first node to an active mode after terminating the at least one second node, wherein the at least one second node in the active mode subscribes to the master message queue, and wherein the at least one second node in the active mode sends acknowledgment messages.