Insights into Company
← Apache Kafka

Architecture Patterns

Understand the idea. Compare it. Explain it. Test yourself.

Question 1 of 10

How do you fix a hot partition?

Solution and explanation

  • Improve keys, salt carefully, add partitions and preserve ordering requirements.
Practice explaining this
Question 2 of 10

How are null-key records partitioned?

Solution and explanation

  • Behavior varies by client; do not rely on null keys for business ordering.
Practice explaining this
Question 3 of 10

How do you order bank account events?

Solution and explanation

  • Key deposit, withdrawal and balance events by accountId.
Practice explaining this
Question 4 of 10

Where does Kafka fit in banking?

Solution and explanation

  • It distributes notification, fraud, audit and integration events; it is not the ledger.
Practice explaining this
Question 5 of 10

What is the transactional outbox pattern?

Solution and explanation

  • Write business data and an outbox event atomically, then publish the outbox to Kafka.
Practice explaining this
Question 6 of 10

What problem does an outbox solve?

Solution and explanation

  • It prevents database success with a lost Kafka event.
Practice explaining this
Question 7 of 10

How does Kafka support order processing?

Solution and explanation

  • orders.created independently drives payment, inventory, shipping, notification and analytics.
Practice explaining this
Question 8 of 10

What if one downstream service is unavailable?

Solution and explanation

  • Other groups continue and the service resumes from its committed offset.
Practice explaining this
Question 9 of 10

REST versus Kafka?

Solution and explanation

  • REST is typically synchronous; Kafka is asynchronous, durable and decoupled.
Practice explaining this
Question 10 of 10

Should Kafka replace REST?

Solution and explanation

  • No; production systems commonly use both at different boundaries.
Practice explaining this