A partition key defines both the ordering boundary and the load distribution. Use the smallest business entity that truly requires ordered events, then test its skew.
The right way to learn Kafka is to build a tiny log broker — not a fake queue with ack/delete. One topic, one log file, one offset per consumer group. That is the whole model.
Most Kafka vs RabbitMQ comparisons say it depends and stop there. This article cuts through the noise by asking one key question about what your system is actually trying to preserve, and maps that directly to the right tool.
"Kafka is fast" is correct but too abstract. Here is the concrete version: four cheap operations that explain why Kafka handles millions of messages without breaking a sweat.