A few weeks ago, the newest version of Red Hat JBoss AMQ was released. AMQ 7 is the result of Red Hat’s efforts on creating a unified messaging platform for its middleware offerings. One of the most interesting features of this new version is the new backing strategy for failovering when configured in high availability. This feature allows clients connections to migrate from one server to another in the event of server failure so client applications can continue to operate.
AMQ 6.x already had an option to configure failover using a shared store, usually backed up by a shared filesystem or a JDBC connection to a database. However, that option involved the use of external infrastructure add-on in hardware and software, representing an increase in overall deployment costs.
In AMQ 7, support for network-based replication was added. When using replication, the live and the backup servers do not share the same data directories; all data synchronization is done over the network. Therefore, all (persistent) data received by the live server will be duplicated to the backup.
Continue reading “Demonstrating Red Hat JBoss AMQ 7 HA Replication Failover”
Most of the time, when we think about collecting, parsing and storing Logs, the first thing that pops in our mind is the ElasticStack or ELK. It is well positioned in developer and sysadmin’s minds. The stack combines the popular Elasticsearch, Logstash and Kibana projects together to easy the collection/aggregation, store, and visualization of application logs. As an Apache Camel rider and Infinispan enthusiast, I prepared this exercise to produce my own log collector and store stack using Red Hat’s products, JBoss Fuse and JBoss Data Grid, instead.
Continue reading “Implementing a Log Collector using Red Hat JBoss Fuse and Red Hat JBoss Data Grid”
As many of you already know, a couple of weeks ago, on April 25, 2017, Red Hat announced it’s fully containerized API Management Platform On-Premises version. Alongside the Software as a Service (SaaS) version, the 3Scale Openshift-based on-premise version opens new opportunities with customers looking for more control over their private APIs. Deploying API Management in their own data center or self-managed cloud environment is part of a critical path.
Continue reading “HOW-TO setup a 3scale AMP on-premise all-in-one install”