Compare Kafka Connector and Atlas Stream Processing

This section provides a comparison of the feature sets of the MongoDB Kafka Connector and Atlas Stream Processing to help you identify which tool best suits your use case.

Feature	Kafka Connector	Atlas Stream Processing
Supported Stream Processing Capabilities	To process streaming data handled by Kafka Connector, you must do one of the following: - Extend the Kafka Connector with SMTs or custom Java - Use or write external tooling	Available through the MongoDB aggregation framework, with extensions specific to stream processing.
Installation	Installation required either locally or on Confluent.	No installation required.
Connectivity Tooling	MongoDB Java Driver required.	Connection managed by Atlas.
Hosting	Hosting required for your Apache Kafka cluster and the Kafka Connector. Use partner services, such as Confluent Cloud, Amazon Managed Streaming, or Redpanda Cloud when possible.	Stream processing functionality fully managed by Atlas. Hosting required for your Apache Kafka cluster.
Windowing	No support for windowing. You must manually configure windowing with the Kafka Streams API or other external tooling.	Support for highly configurable windows.
Connection Type Support	Kafka clusters Atlas databases Atlas collections	Kafka clusters Atlas MongoDB clusters Atlas databases Atlas collections HTTPS
Security Features	SSL/TLS X.509 AWS IAM User must develop all other authentication tools	SSL/TLS X.509 VPC Peering with AWS Private Link with AWS Confluent Private Link with AWS MSK Private Link with Microsoft Azure Event Hub
Pricing	Pricing dependent on your hosting provider.	Hourly pricing managed by Atlas Stream Processing. Typical costs approximately 25% of the cost of the Kafka Connector.

Back

Migrate from Kafka Connect MongoDB

Troubleshooting