Author Archives: Stanislav_Panteleev

The question is – how to create components ? There are 3 basic principles. Summary Table Principle Focus Key Question Addressed REP Reusability & Release Can this component be reused and released independently? CCP Cohesion Do classes that change together … Continue reading →

1. Single Responsibility Principle (SRP) Definition: A class should have only one reason to change. Meaning: Each class should only have one responsibility or functionality. This makes the system easier to maintain and understand. Example: Bad: A Report class that … Continue reading →

https://leetcode.com/problems/lemonade-change/description/

2224. Minimum Number of Operations to Convert Time

Command Query Responsibility Segregation EventSourcing Eventual Consistency (if one database instance updated, other ones should too, there is a listener pattern under hood) Stability patterns circuit breaker Retry pattern Also there is stability based on pos metrics, like health for … Continue reading →

DDD is one o architect patterns Ubiquituis language Ubiquitous Language is a core concept in Domain-Driven Design (DDD) that emphasizes the creation of a common language between all stakeholders involved in a project, such as domain experts, developers, and end-users. BoundedContext … Continue reading →

in mysql we can do smth like this

The Dependency Inversion Principle (DIP) states that high level modules should not depend on low level modules; both should depend on abstractions. Abstractions should not depend on details. Details should depend upon abstractions. flow without dependency inversion, main call high level … Continue reading →

What does this history lesson on paradigms have to do with architecture?Everything. We use polymorphism as the mechanism to cross architecturalboundaries; we use functional programming to impose discipline on the location ofand access to data; and we use structured programming … Continue reading →

example