Kafka is an open-source distributed event and stream-processing platform built to process demanding real-time data feeds. It is inherently scalable, with high throughput and availability.
By default, you are limited to 10 clusters per account or team. If you reach this limit but need to create more clusters, you can submit a request for a higher limit by clicking “Request Increase” on the window that shows when you attempt to create another cluster.
You cannot delete the default database and user.
VPC networks are only available to resources, accounts, and teams in the same region as the VPC network.
You cannot currently add DigitalOcean Cloud Firewalls to a database cluster’s trusted sources.
By default, clusters only support up to 200 IP addresses as trusted sources. Different types of resources add varying numbers of IP addresses to your cluster. For example, Droplets typically have two IP addresses, one public and one private, both of which count towards the 200-address maximum. To add more than 200 IP addresses, contact support.
You cannot migrate databases from clusters inside of DigitalOcean to other clusters inside of DigitalOcean using the online migration feature.
DigitalOcean Kafka does not currently support backups, forking, importing, connection pooling, migration, or PITR.
Each cluster is limited to 15 nodes.
We only support Kafka v3.4, v3.5, and 3.6.
| Kafka Version | EOL Date |
|---|---|
| 3.4 | 2024-05-13 |
| 3.5 | 2024-07-31 |
| 3.6 | 2024-10-18 |
To maintain cluster stability, users cannot use the root user.
Additional storage can cause slight performance degradation in database clusters.
App Platform does not currently support Kafka integration. This includes adding an app as a trusted source to a Kafka database cluster.
Point-in-time-recovery (PITR) operations are limited to the last 7 days. The date picker doesn’t restrict you from choosing an earlier date; you will receive an error if you try to recover from a date outside of the 7-day window.
You can’t use DigitalOcean’s Cloud Firewalls with managed databases. Until support is available, you can restrict access to nodes by their incoming IPv4 addresses. You can also add Droplets and other resources by their names or tags to a cluster’s trusted sources.