Imagine you are building a shared distributed system that needs to store and retrieve data across multiple servers. One of the main challenges is deciding which server should be responsible for storing a given piece of data. Traditional approaches like modulo-based hashing often lead to inefficient data distribution and expensive…

Understand the best memory settings for your AWS Lambdas and optimize for faster runtime or costs based on your business needs! — Prerequisite: AWS Account AWS CLI Access Terraform CLI Introduction AWS Lambda Power Tuning is a tool that helps you optimize the performance of your Lambda functions by automatically running them at different memory allocations and measuring the results. This can help you find the optimal memory allocation for your function, which can…

Scalability stands as a crucial tenet that underpins the design and development of systems, applications, and infrastructure. Scaling is a default in today’s world of distributed systems and while we can scale our services easily(assuming they’re stateless!), the same cannot be said for our stateful systems like data-stores. In this…

The Command Query Responsibility Segregation (CQRS) pattern is a software architecture pattern that separates the responsibility of commands(write operations) and queries(read operations) into two separate models. It emphasizes the idea that the operations to retrieve data (queries) should be treated differently from the operations that modify data (commands). By separating…

The Ambassador design pattern is an architectural pattern that enhances communication between components in a distributed system. It acts as a mediator, isolating communication logic and reducing complexity within the system. The key idea behind the Ambassador pattern is to have a dedicated component (the ambassador) that manages interactions between…

The Sidecar pattern is a design pattern that focuses on extending the functionality of a primary service by attaching an auxiliary container, known as a “sidecar” to it. This sidecar container runs in the same context as the main service and enhances its capabilities without requiring any modifications to the…

The Backends for Frontends (BFF) pattern is an architectural pattern that involves creating a separate backend service for each frontend application. This pattern is often used in microservices architectures, where each service is responsible for a specific function. Following the BFF pattern doesn’t mean you’re creating a new backend, but…

Cell-based architecture in computing involves designing systems that consist of interconnected cells, each cell capable of executing tasks independently. Like the cells in a biological organism, these computing cells have their own processing units, memory, and communication capabilities. They operate in parallel, exchanging information and collaborating to solve complex problems…

Explore the implementation, advantages, disadvantages, and important caveats associated with using the SAGA design pattern. — In the realm of distributed systems and microservices architectures, ensuring data consistency and maintaining transactional integrity can be a complex challenge. One of the ways to achieve transactions across distributed systems is 2 Phase Commits, another approach could be to use SAGA Pattern.