There are a lot of articles about Apache Kafka[1] regarding how companies are using it, what kind of problems Apache Kafka solves, how to create producers and consumers etc. Instead of directly jumping on those (will explore those in the future posts for sure though), let’s look at why it was built and why it’s faster than other messaging solutions. What is Log? The very first line of the Kafka paper[2] says...
Jay Gandhi
Hey there👋 I am a Software Engineer (individual contributor) with 8+ years of experience with a background in full-stack development and big data solutions. Passionate about developing great product offerings with great people and great teams. Interested in system engineering, software development, UI/UX and product management.Notes on Write Amplification versus Read Perspiration
This was shared by one of the colleagues on Relog server on Discord. The discussion was about how log-structured based databases are not meant to have a 1:1 read per write ratio. There are various ways to tune the data structure to favor one over the other. You can read the original article from here. About Pat, He is one of the top publishers in different subject areas like distributed architecture, database transaction processing, etc....