In this article, we will use a Python-based messaging client to connect and subscribe to a topic with a durable subscription in the Apache ActiveMQ Artemis broker. We will use the text-based STOMP protocol to connect and subscribe to the broker. STOMP clients can communicate with any STOMP message broker to provide messaging interoperability among many languages, platforms, and brokers.
If you need to brush up on the difference between persistence and durability in messaging, check Mary Cochran’s article on developers.redhat.com/blog.
A similar process can be used with Red Hat AMQ 7. The broker in Red Hat AMQ 7 is based on the Apache ActiveMQ Artemis project. See the overview on developers.redhat.com for more information.
Continue reading “Using the STOMP Protocol with Apache ActiveMQ Artemis Broker”
We are excited to announce a Developer Preview of Red Hat AMQ Streams, a new addition to Red Hat AMQ, focused on running Apache Kafka on OpenShift.
Apache Kafka is a leading real-time, distributed messaging platform for building data pipelines and streaming applications.
Using Kafka, applications can:
- Publish and subscribe to streams of records.
- Store streams of records.
- Process records as they occur.
Continue reading “Announcing AMQ Streams: Apache Kafka on OpenShift”
Red Hat JBoss AMQ 7 provides fast, lightweight, and secure messaging for internet-scale applications. In addition, AMQ 7 components use industry-standard message protocols and support a wide range of programming languages and operating environments.
Therefore, AMQ 7 gives you the strong foundation you need to build modern distributed applications. Especially relevant is that multiple instances of AMQ 7 brokers can be grouped together to share message processing load.
Each broker manages its own messages and connections and is connected to other brokers with “cluster bridges” that are used to send topology information, such as queues and consumers, as well as load balancing messages.
AMQ 7 supports two different strategies for backing up a server: shared store and replication.
Continue reading “Automating AMQ 7 High Availability Deployment”
Want insights into how other organizations are building cloud-native applications and microservices? At Red Hat Summit 2018, developers from a number of different companies will be sharing their stories in break-out sessions, lightning talks, and birds-of-a-feather discussions. Learn how they solved real business problems using containers, microservices, API management, integration services, and other middleware.
Join us at Red Hat Summit 2018, to hear speakers from Bell Canada, BMW, BP, Deutsche Bank, InComm, Sabre, SIA, Swiss Railways, USAA, and many more.
Continue reading “Red Hat Summit 2018: Learn how other developers are producing cloud-native applications”
It was more than 2 years ago that I blogged about building a Managed File Transfer (MFT) solution using Fuse and AMQ. First, many things have progressed, particularly the technology landscape. Second, MFT protocols have evolved. AS4 provides a new and improved way of securely exchanging documents over HTTP. In addition, the OASIS consortium governs a vendor-neutral open standard. This is great news, but how do we achieve support for these new standards and transports with our antiquated, legacy, and proprietary MFT software?
Continue reading “Managed File Transfer (MFT) 2.0 with Fuse, 3scale and AMQ”
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”
For businesses looking to build scalable Internet of Things (IoT) solutions using containers, here is a sample project built on the Red Hat OpenShift Container Platform. This project implements an intelligent IoT gateway on the OpenShift Container platform. The IoT Gateway is critical for enterprise IoT as it brings intelligence, and enables key services, at the edge. In this project, the gateway application is deployed as a set of microservices inside containers on OpenShift.
Continue reading “How to build a containerized IoT solution with OpenShift”
Our Red Hat Developers program team has just concluded a “Time to Hello World” project to reduce the time it takes you to download and install a new technology, and then get to your first “hello world” application. By utilizing multiple resources from Red Hat engineering, UX, evangelists, docs, testing, and yes, even customers, this is just one of many Red Hat activities underway to minimize speed bumps when trying a new Red Hat technology.
So, is 6 minutes quick enough to try out a new technology? If so, read on.
Continue reading “You had me at Hello, World”
Messaging with JBoss A-MQ (broker), AMQP (protocol), and AMQP.Net Lite (Windows client) Made Easy
This year at Red Hat Summit, I was part of a team whose objective was to create a running, IoT-focused system, at some scale (hundreds of beacons, millions of events), based on a real-world use case to demo live, on stage during the middleware keynote at Red Hat Summit.
Our team chose the area of asset tracking, where important machines, tools or equipment (think mobile ultra-sound machines in hospitals) need to be located on demand and tracked for their usage each day, week, month, year. But, for our demo, instead of machines, we asked Red Hat Summit attendees to participate as our “assets” by wearing Bluetooth Low Energy (BLE) beacons to track their movement throughout the conference.
Continue reading “Behind the Internet of Things Middleware Demo at Red Hat Summit”