APACHE PULSAR SUPPORT & CONSULTING

Unified Messaging and Event Streaming with Apache Pulsar

With our partners, we help organisations adopt Apache Pulsar through architecture consulting, implementation, migration, optimisation, and production support.

TALK TO US ABOUT APACHE PULSAR

Apache Pulsar is a cloud-native, open-source platform that unifies message queuing and event streaming in a single, scalable architecture. It enables organiSations to build reliable, real-time applications for microservices, IoT, AI, financial services, and other event-driven workloads.

MESSAGE QUEUING

Apache Pulsar delivers enterprise-grade message queuing with built-in durability, scalability, and flexible delivery semantics. Common use cases include:

  • Microservice communication
  • Order and payment processing
  • Background job processing
  • Enterprise application integration
  • Task queues
  • IoT device messaging
  • Event notifications

EVENT STREAMING

Apache Pulsar also provides high-performance event streaming for organizations building real-time data platforms. Typical streaming use cases include:

  • Real-time analytics
  • Customer activity streams
  • Change Data Capture (CDC)
  • Data lake and lakehouse ingestion
  • AI and machine learning pipelines
  • Fraud detection
  • Streaming ETL
  • Log aggregation

KAFKA COMPATIBILITY

“Apache Pulsar can speak the Kafka protocol through a Kafka-compatible protocol handler (Kafka-on-Pulsar), letting many existing Kafka producers, consumers, and applications connect to Pulsar with little to no code changes.

This lets organisations modernise their messaging infrastructure while preserving the Kafka skills, tooling, and application investments they’ve already made.”

Frederic | Senior Engineer

What We Offer

Apache Pulsar expertise – from architecture through production.

Whether you’re evaluating Apache Pulsar, migrating from another messaging platform, or scaling an existing deployment, Seventh State, through our vetted partners, provides expert consulting across the entire lifecycle. We help organisations build reliable, cloud-native messaging and event streaming platforms with confidence.

What this looks like in practice:

PULSAR ARCHITECTURE & ASSESSMENT

Evaluate whether Apache Pulsar is the right platform for your workload. We help design scalable architectures, compare migration options, and establish production-ready deployment strategies before implementation begins.

MIGRATION PLANNING & MODERNISATION

Whether you’re migrating from Kafka, RabbitMQ, ActiveMQ, IBM MQ, or legacy JMS applications, we develop phased migration strategies that minimize risk and enable zero or low-downtime cutovers.

PULSAR IMPLEMENTATION

From cluster deployment and security to topic design, schema management, geo-replication, Pulsar IO, and Functions, we help implement a production-ready Apache Pulsar platform following industry best practices.

OPERATIONS & ENABLEMENT

We help your teams operate Apache Pulsar with confidence through observability, performance tuning, upgrades, operational best practices, documentation, and hands-on knowledge transfer

Why Seventh State?

No tunnel vision

Our experience spans RabbitMQ, NATS, Kafka, and Pulsar. When scope shifts or a decision needs to be made mid-engagement, there’s someone in your corner who can evaluate it independently.

No guesswork

Apache Pulsar specialists know Pulsar. We know how Pulsar fits alongside RabbitMQ, NATS, and the rest of your messaging estate.

That broader architectural view is what we bring to every engagement, whatever the technology.

No hand offs

One relationship throughout. We oversee delivery, manage the partner relationship, and stay accountable for the outcome.


One relationship. The full capability map behind it.

Partner Stories

a person pressing on a payment terminal

How Iterable scaled billions of customer messages with Apache Pulsar

Iterable powers customer engagement for some of the world’s leading brands, processing billions of email, SMS, push, and in-app messages every day. As customer growth accelerated, the company needed a messaging platform capable of supporting massive scale while reducing operational complexity. Apache Pulsar provided the enterprise-grade messaging capabilities, scalability, and reliability needed to modernize Iterable’s infrastructure. Using a phased migration approach, Iterable successfully transitioned production workloads while maintaining uninterrupted service for customers.

The outcome:

  • A future-ready platform built for continued growth
  • Billions of customer messages processed every day
  • Nearly 50% reduction in messaging infrastructure costs
  • Highly scalable message queuing architecture
  • Simplified operations and improved reliability

How Cisco modernized its global IoT messaging platform

Cisco IoT Control Center manages hundreds of millions of connected devices across multiple continents. As the platform continued to grow, Cisco needed a messaging architecture that could scale globally while supporting a cloud-native operating model. Apache Pulsar became the foundation of Cisco’s next-generation messaging platform, replacing legacy message queue services as part of a two-year modernization initiative. Today, Pulsar runs across multiple Kubernetes clusters, delivering the scalability, resilience, and operational simplicity required for one of the world’s largest IoT platforms.

The outcome:

  • Hundreds of millions of IoT devices supported globally
  • Cloud-native messaging architecture
  • Multi-cluster Kubernetes deployment
  • Greater scalability and operational resilience
  • Foundation for future platform growth
Let’s talk…

Whether you’re evaluating Apache Pulsar, deploying a new cluster, or migrating from Kafka, RabbitMQ, ActiveMQ, or IBM MQ, we can help

Alternatively:

 Email us: sales@seventhstate.io

 Call us: (+44) 02045725726

 Book a meeting: in the calendar

Frequently Asked Questions

What is Apache Pulsar and how does it compare to Kafka?

Apache Pulsar is a cloud-native messaging and event streaming platform that combines message queuing and event streaming within a single architecture. Unlike Kafka’s tightly coupled storage and compute model, Pulsar separates compute (brokers) from storage (Apache BookKeeper), allowing each to scale independently. Pulsar also includes features such as multi-tenancy, geo-replication, tiered storage, and multiple messaging patterns out of the box, making it well suited for organizations building modern event-driven platforms.

When should I consider moving to Apache Pulsar?

Organisations typically evaluate Apache Pulsar when they need a single platform for both messaging and event streaming, require independent compute and storage scaling, operate across multiple regions or tenants, or are modernizing legacy messaging systems such as Kafka, RabbitMQ, ActiveMQ, or IBM MQ. Pulsar is particularly attractive for cloud-native applications that demand high availability, operational simplicity, and long-term scalability.

What types of workloads is Apache Pulsar best suited for?

Apache Pulsar supports a broad range of real-time workloads, including event streaming, enterprise message queuing, microservices communication, IoT platforms, financial services, AI and machine learning pipelines, log aggregation, Change Data Capture (CDC), and real-time analytics. Its unified architecture allows organizations to support multiple messaging patterns on a single platform.


Can Apache Pulsar support existing Kafka applications?

Yes. Apache Pulsar provides Kafka protocol compatibility through its Kafka compatibility layer, allowing many existing Kafka producers, consumers, and client applications to connect to Apache Pulsar with minimal application changes. This enables organisations to modernise their infrastructure while preserving existing Kafka skills and tooling where appropriate.

Can Apache Pulsar and Kafka run together during a migration?

Yes. Many organisations adopt a phased migration strategy where Apache Pulsar and Kafka operate side by side. Applications can be migrated incrementally using dual publishing, staged consumer migration, and workload validation before production cutover. This approach minimises operational risk while allowing teams to validate the new platform gradually.

What does a migration to Apache Pulsar typically involve?

A typical migration begins with an assessment of the existing messaging architecture, applications, and operational requirements. From there, we design a phased migration strategy that may include cluster deployment, topic and namespace planning, data migration, application validation, and gradual production cutover. The goal is to minimise disruption while modernising the messaging platform.

Is Apache Pulsar a replacement for RabbitMQ?

For some organisations, yes. Apache Pulsar supports traditional message queuing patterns while also providing enterprise-scale event streaming capabilities. Teams looking to consolidate multiple messaging technologies often choose Pulsar as a unified platform that supports both queue-based and streaming workloads without requiring separate infrastructure.