Skip to content

Latest commit

 

History

History
65 lines (36 loc) · 2.1 KB

eventstreams087.md

File metadata and controls

65 lines (36 loc) · 2.1 KB
copyright lastupdated
years
2015, 2018
2018-06-06

{:new_window: target="_blank"} {:shortdesc: .shortdesc} {:screen: .screen} {:codeblock: .codeblock} {:pre: .pre}

Choosing between the three APIs (Standard plan)

{: #choose_api}

{{site.data.keyword.messagehub}} supports three APIs on the Standard plan. Here's some information to help you choose which is most appropriate:

Why use the Kafka API?

{: #why_kafka notoc}

** The Kafka API is available as part of both the Standard and Enterprise plans.**

There are a few reasons that you might choose to use the Kafka API over the other interfaces provided by {{site.data.keyword.messagehub}}. These reasons include the following: {:shortdesc}

  • It is easier to integrate your app with existing systems that have Kafka support, for example {{site.data.keyword.IBM}} {{site.data.keyword.streaminganalyticsshort}} and {{site.data.keyword.sparks}}.
  • It offers lower latency and higher throughput than the other APIs.
  • It offers a richer API than the Kafka REST API.

Why use the Kafka REST API?

{: #why_rest notoc}

** The Kafka REST API is available as part of the Standard plan only.**

The Kafka REST API is a convenient interface that can be used in the following situations:  

  • Where a developer wants to get started using {{site.data.keyword.messagehub}}
  • In certain low throughput use cases where latency is not a critical factor
  • For debugging and fault finding

The Kafka REST API is not intended as a high throughput, low latency interface. ​For these types of requirement, we recommend using the Kafka API to connect to and from {{site.data.keyword.messagehub}}. For more information, see Using a Kafka client.

Why use the {{site.data.keyword.mql}} API?

{: #why_mql notoc}

** The MQ Light API is available as part of the Standard plan only.**

The {{site.data.keyword.mql}} API provides an AMQP-based messaging interface for Java™, Node.js, Python, and Ruby. The API is provided for backward compatibility with the earlier {{site.data.keyword.mql}} service.