Mihvoi’s blogs
Explore Our Milestones
-
Mihvoi’s blogs
Philosophy of EverythingSoftware ArchitectureFilosofia lui Mihvoi (romanian, filosofie)Mobile versions:Philosophy of EverythingSoftware ArchitectureFilosofia lui Mihvoi (romanian, filosofie) Read more ⇢
-
Consistency 2/3 – Flow consistency – read-your-writes consistency
2. Consistency, Availability and low Latency in Distributed system (workarounding the CAP/PACELC theorems) Introduction: “1. Cache and Data Consistency in Distributed systems (CAP/PACELC/CRDT)“ TL;DR Full strong Consistency… Read more ⇢
-
Consistency 1/3 – Cache and Data Consistency in Distributed systems (CAP)
Abstract There is always a tension between data Consistency and system Availability when Partitioning a system across datacenters (think CAP). Especially data cache-ing poses interesting challenges. This tension becomes way more acute as… Read more ⇢
-
Philosophy for robots?
As humans are less and less inclines to read long articles, I guess I will need to start writing philosophy for… robots. What would be different in a philosophy for… Read more ⇢
-
Reusable building blocks in software
When we design a building, we usually design it base on plane walls and right angles. Why is that? Sometimes we design a round form, however that becomes way more… Read more ⇢
-
Bounded contexts or consistency contexts?
“Embrace modularity but beware of granularity” (Mark Richards) While using the Microservice architecture in software can buy you some agility if done right, I often see architectures where microservices… Read more ⇢
-
Dependency Inversion for Entities – software architecture
Problem to solve: We create a core software entity, for example a Product – this will become root or parent entity Then we create multiple “child” entities that depend on Product. For example Order and Warranty. We have business rules… Read more ⇢
-
Microservices: Software decomposition is not for performance, it is for the human brain
You can actually prove that most software systems would work faster in a monolith than in a microservice architecture. Just put back together all the microservices in a monolith, mentally.… Read more ⇢