Abstract: A high availability, high performance software component architecture includes a primary configuration and at least one secondary configuration to take over from the primary configuration in the event of a failure thereof. The primary configuration includes at least one task processing component and a first client component and the secondary configuration includes at least one task processing component and one client component. Status data is present in both configurations and services for write access and read access for the task processing components are separated in such a way that status data read requests coming from the client components are divided between the configurations.

Abstract: The present invention relates to a high availability, high performance software component architecture. The architecture comprises a primary configuration (21) and at least one secondary configuration (22) to take over from the primary configuration in the event of a failure thereof, the primary configuration (21) comprising at least one task processing component (28) and a first client component (231) and the secondary configuration (22) comprising at least one task processing component (28?) and one client component (232), the status data (29, 29?) being present in both configurations (21, 22), the services for write access (26, 26?) and read access (27, 27?) to the task processing components (28, 28?) are separated in such a way that the status data read requests coming from the client components (231, 232) are divided up between the configurations.