Posts

Introducing Open Data Movement

Today Solace introduced something we’re calling Open Data Movement. I’m going to do just two things here: define Open Data Movement, and give an example in pictures.

Breaking Down the Term

Each of the words are important and we’ve chosen them carefully.

Open

We see this as meaning free from proprietary lock in. Solace’s approach to real-time data movement favors:

  • Open protocols – the defined and de facto standards that have emerged for posting, messaging and streaming, including REST, JMS, MQTT, AMQP 1.0 and WebSockets.
  • Open APIs – where possible, we encourage use of open standard APIs like JMS, Paho or Qpid giving developers and enterprises maximum choice.
  • Open to all the popular cloud environments – Solace works the same in private or public IaaS and PaaS platforms, including Amazon Web Services, Microsoft Azure, OpenStack, VMWare, Cloud Foundry, OpenShift and more.
  • Delivering all the message patterns and classes of service – best effort, guaranteed or transactions for request-reply, publish-subscribe, fanin/fanout, and more
  • Openly integrated with popular DevOps tools – Modern products need to be fully integrated from getting started with shared sample code in GitHub, all the way to automating the test, stage and deployment process in tools like Puppet or Bosh (and everything in between).
Read the rest

Introducing the VMR Community Edition

Today we announced an exciting new version of our Virtual Message Router – the “Community Edition.”

In case you don’t already know and love our VMR, it’s a message broker that runs on general purpose processors or in the cloud. The VMR Enterprise Edition supports your favorite message exchange patterns, qualities of service, open APIs/protocols, and deployment environments – from public and private clouds to virtual machines. And it’s fast: with the V7.2 release all versions of the VMR benchmark at 2-5 times as fast (often even more) as your other choices for message brokering.

This new VMR Community Edition is just as fast and offers all the same features: cloud deployment, JMS, MQTT, REST, guaranteed delivery, unified API and administration, the works! Whatever your favorite Solace messaging feature might be, we haven’t left anything out. In fact, the VMR Community Edition differs from its enterprise sibling only in its lower scaling limits and limited fault tolerance.… Read the rest

What’s New with the Neon Release of MQTT Paho

In June 2016 Eclipse announced the Neon, (1.2.0), release of the MQTT Paho Java API. The new functionality provided is automatic reconnect and offline buffering (allowing publish to be called when the application is not connected) for the C, Java, JavaScript and Android clients.  As well as WebSockets support for Java, Python.

Solace continues to support open standards and open APIs by investing engineering effort to ensure these APIs interop in the most efficient manor with the Solace message router. In this blog I will look at the new auto-reconnect, high availability and publish offline features and show how they interop with Solace message broker to provide an end-to-end highly available solution.

Click these links to learn more about Solace’s general support for MQTT or high availability features, or to obtain a full working example on Github.… Read the rest

Solace Integration with Apache Spark MQTT Utilities

apache-spark-mqttPreviously I had published an integration guide to integrate Spark Streaming into the Solace message bus via JMS.  This method of integration provides a plush set of integration options including Topic and Queue messaging patterns as well as enhanced security with TLS.  Integration with Spark Streaming via JMS does require extending the Spark custom receiver to support JMS.

If you are looking for a simple integration without having to write any code, then MQTT might be a better fit for your needs, as the Apache Spark that is distributed with Hortonworks, Cloudera and other Hadoop releases comes with a streaming MQTT interface built in.  As of SolOS 7.1.1, Solace makes it easy to integrate MQTT clients into the Solace message bus.   Spark provides the MQTTUtils Class that wraps up and provides a simple interface to receive messages from an MQTT broker and maps received messages into a Spark context.  The MQTTWordCount example that comes with Spark 1.4 and above shows how this is done.… Read the rest

Getting the Most from Open Source, Open Standards and Solace

linux and openmamaWith Solace technology being used more and more alongside open source products, and with open standard protocols, we’ve been hard at work expanding our interoperability with complementary technologies to give our customers maximum choice and help them avoid vendor lock-in.

Earlier this year, we announced support for MQTT, an OASIS standard protocol within the Internet of Things, and support for REST as a first class messaging protocol. We’ve also worked with clients to connect Solace with Flume, Spark and Storm as means of  gathering data across the enterprise and making big data more real time.

This week, we were part of two more announcements that highlighting this effort:

  • On Tuesday the Linux Foundation announced their newest members, including Solace, CloudLinux and MariaDB. The Linux Foundation is at the heart of much of the open source movement, and we look forward to participating in the growth and adoption of these technologies.
Read the rest

oneM2M Aims to set Standards for M2M and IoT

In order to achieve plug-and-play interoperability between connected devices, what’s commonly called machine to machine (M2M) communications or the Internet of Things (IoT), there needs to be agreed-upon standards for connectivity, security and information sharing between the devices and back-end applications.

The first significant step in that direction came earlier this month when oneM2M, a global organization of over 200 companies, published a set of 10 documents that propose standards for IoT architecture, security, service definition, management, and specifying protocol bindings to the most commonly used IoT protocols CoAP, MQTT and HTTP.

The momentum behind this initiative is encouraging, and it’s good to see such an apparently complete standard proposed relatively early in the evolution of IoT. The devil will be in the details as we learn how comprehensive the specifications are, and to what degree early adopters must extend them to deliver production grade systems.

Still, something is better than nothing.… Read the rest