Educative tuesday(Apache Kafka): fundamental idea around kafka in order to scale messages sent and received by kafka require a user specified user strategy basically the user needs to specify on how we distribute events across our different partitions

Consumers (in groups) subscribe to topics and process messages in parallel Kafka Retries & Errors (Short) Producer Automatically retries temporary errors (network, leader election, etc.). Key settings: retries, retry.backoff.ms, delivery.timeout.ms. Enable enable..

educative tuesday : Database sharding and partitioning are not the same both split large data into smaller pieces for better performance and management, but they differ in where the pieces live.

Partitioning (simpler, usually one machine) :- You take one big table and break it into smaller partitions (chunks) These partitions usually stay inside the same database on the same server. Common ways: by date range (e.g., one partition per month), by region, by hash of a key