Basic – API Request

Path Parameter vs. Request Body Parameter Path Parameter: Use Case: Typically, path parameters are used to identify specific resources. For instance, if you want to add a child node to a specific parent node, using the parent’s node_id as a path parameter (e.g., POST /nodes/{parent_id}/children) clearly indicates the relationship and hierarchy. Best Practice: This aligns with REST principles… Continue reading Basic – API Request

KEDA (Kubernetes-based Event Driven Autoscaling)

KEDA (Kubernetes-based Event Driven Autoscaling) is a CNCF (Cloud Native Computing Foundation) project that enables event-driven and queue depth-based autoscaling for workloads running in Kubernetes. It allows Kubernetes deployments to scale up or down based on the rate of incoming messages or the depth of various message queues, such as Kafka, RabbitMQ, or Azure Service… Continue reading KEDA (Kubernetes-based Event Driven Autoscaling)

Kafka – incremental cooperative rebalance protocol

The incremental cooperative rebalance protocol was introduced in Kafka 2.4.0, which supports KIP-429. Starting with this version, Kafka clients can opt to use this protocol for consumer groups to achieve more efficient and less disruptive rebalancing.To enable the incremental cooperative rebalancing protocol, the consumer's partition.assignment.strategy configuration should be set to use one of the following… Continue reading Kafka – incremental cooperative rebalance protocol

Kafka Parallel Processing

Uber - https://www.uber.com/en-IN/blog/reliable-reprocessing/https://www.uber.com/en-IN/blog/kafka-async-queuing-with-consumer-proxy/ Confluent - https://www.confluent.io/blog/introducing-confluent-parallel-message-processing-client/https://github.com/confluentinc/parallel-consumer?tab=readme-ov-file 21 min in video to understand offset management in kafka parallel https://play.vidyard.com/5MLb1Xh7joEQ7phxPxiyPK.jpg

DynamoDB

When you perform an UpdateItem operation using the DAX client, the update is processed as a write-through operation. This means that the item is updated in both DynamoDB and the DAX cache simultaneously. How DAX Handles Updates Immediate Update in DAX: When you execute an UpdateItem via the DAX client, DAX first updates the item in the underlying DynamoDB table. Once… Continue reading DynamoDB

Cursor vs Offset Based Pagination

CriteriaCursor-Based PaginationOffset-Based Pagination PerformanceExcellent for large datasets, as it avoids the overhead of calculating offsets for deep pagination.Degrades with large datasets or high offsets, as scanning through previous pages becomes expensive. Consistency in Dynamic DataHighly consistent in environments with frequent data changes; avoids skipping or duplicating items.Prone to skipping or duplicating items when the dataset… Continue reading Cursor vs Offset Based Pagination