An individual recounts the worst architectural decision made to use Kafka for multiple unconventional purposes.
Two years ago, during the development of a high-traffic e-commerce platform, the team decided to leverage Apache Kafka meant for event streaming for various other functionalities.
The Kafka cluster was repurposed as a database, cache, job queue, configuration store, session manager, and DNS resolver, leading to a heavyweight usage outside its intended scope.
This decision highlights the unintended consequences of convenience and the importance of utilizing tools for their designated purposes.