Why design a system around a producer/consumer split (e.g. an inventory-update producer and a search-index consumer) instead of one service doing everything?

Splitting them lets each service scale, deploy, and fail independently — a slow search-indexing process doesn't block inventory updates from being accepted, and if the indexing consumer crashes, events simply queue up in Kafka until it recovers, rather than inventory updates themselves failing.