Case study: a synchronous fraud check over Kafka and Redis — good idea or not?
Reviewing a wallet service that waits for a fraud verdict over Kafka and uses Redis to match replies to requests: the message envelope, events vs commands, eight design problems, the alternatives (ReplyingKafkaTemplate, per-instance reply partitions, HTTP with a timeout, an asynchronous UX) and the transactional outbox.