<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chris Bartholomew on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/chris-bartholomew/</link><description>Articles written by Chris Bartholomew on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 05 May 2022 18:11:20 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/chris-bartholomew/index.xml" rel="self" type="application/rss+xml"/><item><title>5 More Reasons to Choose Apache Pulsar Over Apache Kafka</title><link>https://foojayio.github.io/website/today/5-more-reasons-to-choose-apache-pulsar-over-apache-kafka/</link><pubDate>Thu, 05 May 2022 18:11:20 +0000</pubDate><guid>https://foojayio.github.io/website/today/5-more-reasons-to-choose-apache-pulsar-over-apache-kafka/</guid><description>&lt;p&gt;&lt;em&gt;Author&amp;rsquo;s note: I originally published this blog post in 2019, while I was CEO of Kesque, a real-time messaging service built on&lt;/em&gt; &lt;a href="https://pulsar.apache.org/" target="_blank" rel="noopener noreferrer"&gt;&lt;em&gt;Apache Pulsar&lt;/em&gt;&lt;/a&gt;
&lt;em&gt;, the cloud-native distributed messaging and streaming platform. It&amp;rsquo;s a follow-up to an earlier post, &amp;ldquo;&lt;/em&gt; &lt;a href="https://datastax.medium.com/7-reasons-to-choose-apache-pulsar-over-apache-kafka-cb111087eadb" target="_blank" rel="noopener noreferrer"&gt;&lt;em&gt;7 Reasons to Choose Apache Pulsar over Apache Kafka&lt;/em&gt;&lt;/a&gt;
&lt;em&gt;.&amp;rdquo; A lot of big changes have happened since these two posts went live, including Kesque&amp;rsquo;s&lt;/em&gt; &lt;a href="https://www.datastax.com/press-release/datastax-delivers-scale-out-enterprise-event-streaming-modern-data-apps" target="_blank" rel="noopener noreferrer"&gt;&lt;em&gt;acquisition&lt;/em&gt;&lt;/a&gt;
&lt;em&gt;, in January 2021, by DataStax. The reasons to choose Pulsar, however, haven&amp;rsquo;t changed.&lt;/em&gt;&lt;/p&gt;</description></item><item><title>7 Reasons to Choose Apache Pulsar over Apache Kafka</title><link>https://foojayio.github.io/website/today/7-reasons-to-choose-apache-pulsar-over-apache-kafka/</link><pubDate>Wed, 15 Dec 2021 10:03:13 +0000</pubDate><guid>https://foojayio.github.io/website/today/7-reasons-to-choose-apache-pulsar-over-apache-kafka/</guid><description>&lt;p&gt;&lt;em&gt;&lt;strong&gt;I wrote an earlier version of this article in 2019, while I was CEO of Kesque, a real-time messaging service built on&lt;/strong&gt;&lt;/em&gt; &lt;a href="https://pulsar.apache.org/" target="_blank" rel="noopener noreferrer"&gt;&lt;em&gt;&lt;strong&gt;Apache Pulsar&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;
&lt;em&gt;&lt;strong&gt;, the cloud-native distributed messaging and streaming platform. A lot of big changes have happened in the interim; perhaps the most significant of these is the fact that the company I founded in early 2019 was&lt;/strong&gt;&lt;/em&gt; &lt;a href="https://www.datastax.com/press-release/datastax-delivers-scale-out-enterprise-event-streaming-modern-data-apps" target="_blank" rel="noopener noreferrer"&gt;&lt;em&gt;&lt;strong&gt;acquired&lt;/strong&gt;&lt;/em&gt;&lt;/a&gt;
&lt;em&gt;&lt;strong&gt;, in January, by DataStax. One thing that hasn&amp;rsquo;t changed, however, is the rationale behind our choice of Apache Pulsar.&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;</description></item><item><title>Fast JMS for Apache Pulsar: Blazing Performance</title><link>https://foojayio.github.io/website/today/fast-jms-for-apache-pulsar-modernize-and-reduce-costs-with-blazing-performance/</link><pubDate>Fri, 10 Dec 2021 08:54:44 +0000</pubDate><guid>https://foojayio.github.io/website/today/fast-jms-for-apache-pulsar-modernize-and-reduce-costs-with-blazing-performance/</guid><description>&lt;p&gt;DataStax recently announced the availability of &lt;a href="https://github.com/datastax/pulsar-jms" target="_blank" rel="noopener noreferrer"&gt;Fast JMS for Apache Pulsar&lt;/a&gt;
, a JMS 2.0 API. By combining the industry-standard Java Messaging Service (JMS) API with the cloud-native and horizontally scalable Apache Pulsar™ streaming platform, DataStax is providing a powerful way to modernize your JMS infrastructure, improve performance, and reduce costs. Fast JMS is open source and is included in DataStax&amp;rsquo;s Luna Streaming Enterprise support of Apache Pulsar.&lt;/p&gt;
&lt;h2 id="h2-0-what-is-jms"&gt;What is JMS?&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://en.wikipedia.org/wiki/Jakarta_Messaging" target="_blank" rel="noopener noreferrer"&gt;Java Message Service&lt;/a&gt;
 (JMS), or &lt;a href="https://jakarta.ee/specifications/messaging/" target="_blank" rel="noopener noreferrer"&gt;Jakarta Messaging&lt;/a&gt;
 as it is now known, is a standard messaging API that is part of the Java Enterprise Edition (now &lt;a href="https://jakarta.ee/" target="_blank" rel="noopener noreferrer"&gt;Jakarta EE&lt;/a&gt;
) ecosystem. It defines how to create, send, receive, and read messages between loosely coupled producers and consumers.&lt;/p&gt;</description></item></channel></rss>