Abstract: A method and messaging system comprising a master broker computer system, a plurality of slave broker computer systems, and a plurality of event stores, for a broker computer system to change its status from a slave broker computer system to a master broker computer system.

Abstract: A message broker computer includes a master broker, a plurality of slave message brokers and event stores. A client system sends messages for processing to the master broker. The master broker generates a message event in response to receiving such a message, and distributes the message event in parallel to the slave brokers and the event stores. Each of the event stores store the message event in persistent storage, and notifies the master broker that the message event has been persisted. The master broker considers the message stabilized n a quorum of the event stores. As the master broker does not take action until a messaging event is stabilized, in the event of failover, a new master broker is able to re-construct a broker state of the old master with no loss of data.

Abstract: A message broker computer includes a master broker, a plurality of slave message brokers and event stores. A client system sends messages for processing to the master broker. The master broker generates a message event in response to receiving such a message, and distributes the message event in parallel to the slave brokers and the event stores. Each of the event stores store the message event in persistent storage, and notifies the master broker that the message event has been persisted. The master broker considers the message stabilized n a quorum of the event stores. As the master broker does not take action until a messaging event is stabilized, in the event of failover, a new master broker is able to re-construct a broker state of the old master with no loss of data.

Abstract: An apparatus in one example has: a controller having a data connector for inputting temporal data, and an item collection for providing timelines and overlays, and for providing linked visualizations of the temporal data in a timeline to other visualizations of the temporal data; and a display for displaying the timeline and overlays, and the linked visualizations. The method may have the steps of: obtaining temporal data; displaying the temporal data in at least one timeline in a web browser and in at least one other visualization in the web browser; and linking the displayed data in the at least one timeline with the displayed data in the at least one other visualization.

Abstract: A server receives image, graphic and/or analytic data and processes and asynchronously outputs that data to a thin/no client. The server inputs image data in a variety of different formats and renders a normalized format that can be streamed to the thin/no client using light-weight protocol(s). The server updates the image, feature and/or analytic data in real time. The server inputs feature, analytic, business logic and other data and process it into various format(s) that can be streamed to the thin/no client and overlaid on the image data. The server provides application services, which can include collaboration, tracking, alerting, business, workflow and/or other desired services. The server can receive collaboration data from one thin/no client and stream that collaboration data to other thin/no clients to enable shared situational awareness between the thin/no clients. The server includes a programming environment for programming thin/no clients contained within server-based web pages.