Abstract: Service virtualization containers to aggregate service functionality from a plurality of services into an apparent service exhibiting the aggregated functionality. A plurality of service implementations is assigned to a service virtualization container. The container selects some of the service operations from the service implementations. One or more message characteristics are assigned to the service operations in one or more routing tables. A message is received at a service endpoint different from the service endpoints of any of the service implementations. A determination is made of one or more message characteristics. The one or more routing tables are consulted to select a determined service operation based on the message characteristics. The message is routed to the selected service implementation.

Abstract: The present invention extends to methods, systems, and computer program products for automatically re-starting services. Embodiments of the invention can be used to re-start a service when it is determined that the service stopped during the processing pending work. A container manager durably tracks a service's status (busy/idle and alive/dead) and tracks transitions between statuses. Accordingly, when a busy service is deemed dead (due to any event), the container manager can automatically re-start the service. Upon re-start the service can check for pending work and start executing its pending work.

Abstract: The present invention extends to methods, systems, and computer program products for load balancing for services. Embodiments of the invention facilitate load balancing between instances of a service based on affinitization of messages, based on content of the message. For example, messages in the same session can be dispatched to the same service instance. A sequence or series of related messages associated with long running and/or stateful services are more likely to be dispatched to the same instance of the service. Thus, if the service instance has persisted client state, there is an increased likely of utilizing the persisted client state and not having another service instance recreate the client state.

Abstract: The present invention extends to methods, systems, and computer program products for redirecting client messages between hosts within a messaging infrastructure. When a host receives a client message, it can refer to lock information in a shared database to determine if it is the correct host to receive the client message. The lock information includes a redirect endpoint. The redirect endpoint identifies an endpoint where client messages can be sent for delivery to the appropriate workflow instance. The redirect endpoint can be included in a redirect fault message, that is returned to a host when a host attempts to process a client message that is already locked to another workflow instance. Using the redirect endpoint, a host receiving a redirect fault message can use the redirect endpoint to send a client message to the correct host.

Abstract: The present invention extends to methods, systems, and computer program products for redirecting client messages between hosts within a messaging infrastructure. When a host receives a client message, it can refer to lock information in a shared database to determine if it is the correct host to receive the client message. The lock information includes a redirect endpoint. The redirect endpoint identifies an endpoint where client messages can be sent for delivery to the appropriate workflow instance. The redirect endpoint can be included in a redirect fault message, that is returned to a host when a host attempts to process a client message that is already locked to another workflow instance. Using the redirect endpoint, a host receiving a redirect fault message can use the redirect endpoint to send a client message to the correct host.

Abstract: The present invention extends to methods, systems, and computer program products for redirecting client messages between hosts within a messaging infrastructure. When a host receives a client message, it can refer to lock information in a shared database to determine if it is the correct host to receive the client message. The lock information includes a redirect endpoint. The redirect endpoint identifies an endpoint where client messages can be sent for delivery to the appropriate workflow instance. The redirect endpoint can be included in a redirect fault message, that is returd to a host when a host attempts to process a client message that is already locked to another workflow instance. Using the redirect endpoint, a host receiving a redirect fault message can use the redirect endpoint to send a client message to the correct host.

Abstract: The present invention extends to methods, systems, and computer program products for automatically re-starting services. Embodiments of the invention can be used to re-start a service when it is determined that the service stopped during the processing pending work. A container manager durably tracks a service's status (busy/idle and alive/dead) and tracks transitions between statuses. Accordingly, when a busy service is deemed dead (due to any event), the container manager can automatically re-start the service. Upon re-start the service can check for pending work and start executing its pending work.

Abstract: Service virtualization containers to aggregate service functionality from a plurality of services into an apparent service exhibiting the aggregated functionality. A plurality of service implementations is assigned to a service virtualization container. The container selects some of the service operations from the service implementations. One or more message characteristics are assigned to the service operations in one or more routing tables. A message is received at a service endpoint different from the service endpoints of any of the service implementations. A determination is made of one or more message characteristics. The one or more routing tables are consulted to select a determined service operation based on the message characteristics. The message is routed to the selected service implementation.

Abstract: The present invention extends to methods, systems, and computer program products for load balancing for services. Embodiments of the invention facilitate load balancing between instances of a service based on affinitization of messages, based on content of the message. For example, messages in the same session can be dispatched to the same service instance. A sequence or series of related messages associated with long running and/or stateful services are more likely to be dispatched to the same instance of the service. Thus, if the service instance has persisted client state, there is an increased likely of utilizing the persisted client state and not having another service instance recreate the client state.