Immutable State Blog

Mojtaba Kavand


Academic paper, Access by permission.  Go back [home](/).



To enable multiple systems to be integrated using a common leveled facades and interfaces , regardless of the underlying implementation or technology to help organizations build more efficient, adaptable, and scalable software solutions.

Polymorphic Integration


## Introduction

The main goal of a testability framework is to make it easier and more efficient to test software. This is achieved by designing the software in a way that makes it easier to isolate different components and functions, and by ensuring that the software can be easily tested using automated testing tools.

A testability framework may include a number of different elements, such as:

1. Design patterns and principles that promote testability
2. Tools and frameworks for automated testing, such as unit testing frameworks, integration testing frameworks, and acceptance testing frameworks
3. Guidelines for writing testable code and creating test cases
4. Processes for tracking and managing test results and defects

By implementing a testability framework, software development teams can improve the quality of their code, reduce the number of defects, and speed up the development process by catching issues early in the development cycle.


Academic paper, Access by permission.  Go back [home](/).


Set of tools, techniques, and practices used to insure that software is designed and developed with testing in mind.

Testability Framework


Academic paper, Access by permission.  Go back [home](/).


How to trace a request as it travels through different components of a distributed system in a meaningful way.

Distributed Observability in Practice

By Mojtaba Kavand

- License: CC BY for Article, MIT for Code Repos 
- Last revision: Apr 20 2021
- Target Language(s): Rust, C#, Go, Typescript 
- Audience: Engineers (refer to academic perception via the paper series)


## Introduction
The aim is to implement a mechanism to maintain the code per context, per logic suitable for event-driven architecture,
 while we keep the slate harmonic between immutability and mutability by leveraging the power of FP and OOP! 

## Concerns
- To isolate idempotent logics with robust application tier/layer in place.
- To achieve better threading flow.
- Leverage the mutability implication of OOP to tier our application.
- Leverage the immutable flow for static algorithmic snippets by the power of FP.
- CQRS in nature.
- DDD centric.

## What do we mean by a Slice of Logic
Simply the Request tunnel originated by a Command or Query to retrieve a response from the application layer will shape our Slice of 
Logic. 

![Logical slicing](posts/images/logical-slice.png)
 
## Thread Selectors for better threading flow:
Selectors select a slice of logic and handle the thread by generating a command or a query. For instance, each microservices entry layer has a background service holding the selectors. 

Selectors are responsible to assign strongly typed command/query models through command/query shaper to comply with CQRS intuitively.

## OOP and FP in Harmony
FP encourages immutability and purity as much as possible, while OO  built for state and mutation – a slightly organized version of imperative programming. Objects can be immutable, but OO seems to imply state/change.

On the other hand OO is robust in polymorphic behaviour while it keeps state of object mutable. 

The aim is to leverage OOP to tier our code for the sake of better abstraction, encapsulation and polymorphic behaviour, while we apply FP at the tail to code algorithmic scenarios. In this scenario, the Bridge snippet will carry the structured data in a mutable way. 

## FP Bridge
The bridge is a static snippet that moves the structured data from the handler to the FP ground.

![Functional Programming Bridge](/posts/images/functional-bridge.png)
  

Go back [home](/).


The aim is to implement a mechanism to maintain the code per context, per logic suitable for event-driven architecture, while we keep the slate harmonic between immutability and mutability by leveraging the power of FP and OOP!

Harmonic Slicing - Minimum Structure


Academic paper, Access by permission.  Go back [home](/).

Efficient and flexible way to perform complex tasks, automate processes, and access advanced features of any distributed system.

CLI, Why it is important

Understanding the business domain in order to create effective software solutions.

Immutable State Blog

Polymorphic Integration

Testability Framework

Distributed Observability in Practice

Harmonic Slicing - Minimum Structure

CLI, Why it is important

DDD in Practice