approaches to messaging are showing a lot interest recently. It seems plausible that API standards for cloud computing may converge on a REST style set of interfaces and consequently a REST messaging approach loss (even for non-durable messages). This is especially useful in certain environments (e.g. the cloud) where the size of a cluster may change relatively frequently. When scaling up a cluster (i.e. adding suitable for reliably sending messages from one cluster to another, for instance across a WAN, between cloud regions or there internet and where the connection may be unreliable. Federation has built in resilience

loss (even for non-durable messages). This is especially useful in certain environments (e.g. the cloud) where the size of a cluster may change relatively frequently. When scaling up a cluster (i.e. adding suitable for reliably sending messages from one cluster to another, for instance across a WAN, between cloud regions or there internet and where the connection may be unreliable. Federation has built in resilience debug logging for org.apache.activemq.artemis.core.config.impl.ConfigurationImpl to get more insight. securityEnabled=false acceptorConfigurations.tcp.factoryClassName=org.apache.activemq.artemis

loss (even for non-durable messages). This is especially useful in certain environments (e.g. the cloud) where the size of a cluster may change relatively frequently. When scaling up a cluster (i.e. adding suitable for reliably sending messages from one cluster to another, for instance across a WAN, between cloud regions or there internet and where the connection may be unreliable. Federation has built in resilience debug logging for org.apache.activemq.artemis.core.config.impl.ConfigurationImpl to get more insight. There are a growing number of examples of what can be explicitly configured in this way in the

loss (even for non-durable messages). This is especially useful in certain environments (e.g. the cloud) where the size of a cluster may change relatively Clusters 362 frequently. When scaling up a cluster suitable for reliably sending messages from one cluster to another, for instance across a WAN, between cloud regions or there internet and where the connection may be unreliable. Federation has built in resilience debug logging for org.apache.activemq.artemis.core.config.impl.ConfigurationImpl to get more insight. There are a growing number of examples of what can be explicitly configured in this way in the

loss (even for non-durable messages). This is especially useful in certain environments (e.g. the cloud) where the size of a cluster may change relatively frequently. When scaling up a cluster (i.e. adding suitable for reliably sending messages from one cluster to another, for instance across a WAN, between cloud regions or there internet and where the connection may be unreliable. Federation has built in resilience debug logging for org.apache.activemq.artemis.core.config.impl.ConfigurationImpl to get more insight. There are a growing number of examples of what can be explicitly configured in this way in the

loss (even for non- durable messages). This is especially useful in certain environments (e.g. the cloud) where the size of a cluster may change relatively frequently. When scaling up a cluster (i.e. adding suitable for reliably sending messages from one cluster to another, for instance across a WAN, between cloud regions or there internet and where the connection may be unreliable. Federation has built in resilience debug logging for org.apache.activemq.artemis.core.config.impl.ConfigurationImpl to get more insight. There are a growing number of examples of what can be explicitly configured in this way in the

loss (even for non- durable messages). This is especially useful in certain environments (e.g. the cloud) where the size of a cluster may change relatively frequently. When scaling up a cluster (i.e. adding suitable for reliably sending messages from one cluster to another, for instance across a WAN, between cloud regions or there internet and where the connection may be unreliable. Federation has built in resilience debug logging for org.apache.activemq.artemis.core.config.impl.ConfigurationImpl to get more insight. There are a growing number of examples of what can be explicitly configured in this way in the

loss (even for non- durable messages). This is especially useful in certain environments (e.g. the cloud) where the size of a cluster may change relatively frequently. When scaling up a cluster (i.e. adding suitable for reliably sending messages from one cluster to another, for instance across a WAN, between cloud regions or there internet and where the connection may be unreliable. Federation has built in resilience debug logging for org.apache.activemq.artemis.core.config.impl.ConfigurationImpl to get more insight. There are a growing number of examples of what can be explicitly configured in this way in the

loss (even for non- durable messages). This is especially useful in certain environments (e.g. the cloud) where the size of a cluster may change relatively frequently. When scaling up a cluster (i.e. adding suitable for reliably sending messages from one cluster to another, for instance across a WAN, between cloud regions or there internet and where the connection may be unreliable. Federation has built in resilience debug logging for org.apache.activemq.artemis.core.config.impl.ConfigurationImpl to get more insight. There are a growing number of examples of what can be explicitly configured in this way in the

loss (even for non- durable messages). This is especially useful in certain environments (e.g. the cloud) where the size of a cluster may change relatively frequently. When scaling up a cluster (i.e. adding suitable for reliably sending messages from one cluster to another, for instance across a WAN, between cloud regions or where connection may be unreliable. Federation has built-in resilience to failure so if debug logging for org.apache.activemq.artemis.core.config.impl.ConfigurationImpl to get more insight. There are a growing number of examples of what can be explicitly configured in this way in the